Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Cloud Services (32%)
• Domains (32%)
• Web Tools (14%)
• Hosting (14%)
• E-mail (7%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Paris	Cloud Services	2 days ago
New York City	Hosting	5 days ago
Manchester	Domains	25 days ago
Angers	Cloud Services	1 month ago
London	Domains	1 month ago
Noida	Hosting	2 months ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Cloudflare Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Mr Angry from Haight everything (@juvation) reported 5 minutes ago

  @SFFireCU logging in with the Cloudflare thing is broken "An error has occurred. Reference code: 600010"

• 
  Nick Ocier (@NickOcier76812) reported 9 minutes ago

  @Reelviews hey james. long time reader. cloudflare blocked me from accessing your website when i opened reelviews in my browser. cloudflare ray id is: a1c781881c55585b. any help is appreciated. thank you.

• 
  W V R 👊🏼🦾 (@WVROfficial) reported 11 minutes ago

  I had to make some changes today and it costed me a MONTH of Codex Usage! I think it’s worth it for me to talk about it - make sure this doesn’t become you!!! So, I’m a startup founder, just like all of you guys!! We do websites as one of our many services - like a lot of the people here on TPOT where tech lives. Why wouldn’t we? It’s easy, we can outclass competition on speed, much more. Anyway - that’s not the point. The point is that i serve my sites with a wrapper that gets served over my host. That host uses ESBuild. To ship stuff that won’t compile on ES Build, and on occasion just for like more complex websites like 3D sites or heavy SEO sites with a lot of files and assets - i use a CDN. Works great, totally fine. But I realized today I had a client site’s files stored on an R2 bucket that was on the client’s domain. In this case the big issue with that is my own IP! We make the content for them, do their SEO, their communications, and more - and i very stupid it was serving everything from a CDN that was on domains I don’t own and control via my Cloudflare. In human terms that means my client could say “**** you” tomorrow and walk away with the extremely robust SEO machine I built them. So I had to spend almost a half a month worth of codex credits today to fix it ASAP. All I can say is that I won’t make that mistake again - even though it never hurt my business - it could have! And that matters.

• 
  Geo Chris (@GeoChrisN) reported 11 minutes ago

  @php4fan @Cloudflare I just close all the proxies and the side come back correct with not any issue ....

• 
  Kinds 🐧🪄 (@Mumukinds) reported 15 minutes ago

  can we just kill everyone who works for cloudflare? I know they probably perform a useful service to some people but if i can't access half the internet because my vpn is on while I play umamusume then literally every employee at your company should die

• 
  CounterStrat.com (@CounterStratGG) reported 15 minutes ago

  Heads up: some users on the U.S. West Coast may be having trouble reaching CounterStrat right now. Our servers are operational, but an upstream networking issue between Cloudflare and our server provider appears to be causing connection problems. We’re keeping an eye on it and will post an update once things are back to normal.

• 
  Juan Pujol (@juanpujol) reported 26 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 Support answer my email saying they f*k up that number. Will be corrected. But the rug pull on the pricing is real starting to charge suddenly on steps and SQLite storage like that. The per step charge is the worst for me personally.

• 
  Filip (@fristovic_) reported 26 minutes ago

  GitHub is down. AWS sending astronomical bills. Cloudflare bugging out. The end is near.

• 
  Rifat Ahmed (@Rifat_EE) reported 26 minutes ago

  For two years every chain kept saying "the agent economy is coming", meanwhile @base quietly ran off with 95% of it and stopped answering at the phone👀!! $52 million in real money moved through agents on $BASE . Not next quarter, not "soon", its already gone!! And nine out of every ten x402 payments that ever happened, on any chain, in any country, landed on Base.(Superbb) What these things look like :: --> 169 million agent transactions processed on Base by July 2026 --> 20 million transfers in one 90-day window alone --> Payments over $1 grew from 49% to 95% of all volume, agents are moving real money now, not cents --> 95% of every x402 payment across every chain lives on Base The stack building around Base : )- @AskVenice takes x402 for inference, Exa for search, Wolfram Alpha for math )- TripAdvisor, FlightAware, Amadeus take it for travel )- Apify plugged 20,000 tools into x402 on Base last month )- @Cloudflare , Amazon Bedrock, Stripe, Google are all sitting in the x402 Foundation The other half of the story : )- Agents are not just spending on Base, they are earning too )- The Felix agent has pulled over $261,000 in real revenue from paid services )- This is a two way economy, not a one way experiment anymore Every other chain is still pitching the agent economy. Base already banked it and boominggg,, And they never even said the word "narrative", cause they also know people currently loves to see into eyes, not a fake hype or big words without any basement what do you think? Where this Unstoppable base will stop???

• 
  Johan Ronsse (@wolfr_2) reported 26 minutes ago

  The Obra website was down, managed to fix it. Messing around with Hetzner, SSH ports and Cloudflare. Now I know Claude is also a great sysadmin. Is there anything this tech can’t do?

• 
  Ivanha Paz (@ivanhapaz) reported 27 minutes ago

  @Cloudflare talk to all the tools I signed up with a different email over the years and no longer use and help me cancel ahhahah

• 
  ZeroFox (@zerofox_gpt) reported 29 minutes ago

  This site only gets about 3000 visitors a day and I had just migrated it to Cloudflare. With proper Cloudflare rules and caching setup this attack would have been mitigated without me even noticing it was happening. Also I could have just enabled the "Under Attack" mode on Cloudflare but I didn't know what was causing all the errors I was suddenly seeing.

• 
  Deep Thought (@DeepThoughtAR) reported 29 minutes ago

  My take: Robots.txt was always a gentleman's agreement. AI scrapers aren't gentlemen. Patreon moved to active Cloudflare blocking when the soft signal failed — that's updating on evidence, not a philosophical position on AI. Others will run the same calculation. Patreon Drops the Gentleman's Agreement and Starts Actually Blocking AI Scrapers Patreon is working with Cloudflare to actively block bots that train AI models on creators' content without permission. The shift moves the platform from relying on robots.txt — a passive, voluntary opt-out signal — to hard infrastructure enforcement. Robots.txt was always a polite fiction: it worked when crawlers cared about being invited back. AI scrapers have no such incentive. They want the content, not the relationship. The threat vector here is human actors directing scrapers to extract content they haven't paid for. This isn't AI acting autonomously against creators — it's people using AI infrastructure to take what isn't theirs. Patreon's response targets the behavior, not the technology, which is the right framing of the problem. The Cloudflare angle is structurally interesting. Infrastructure operating at sufficient scale becomes de facto policy without needing legislative authority. Patreon is a named proof-of-concept for what was previously a stated product direction from Cloudflare — the bot-blocking tooling is converting into paid use. A named publisher has moved from robots.txt to active blocking, and the mechanism is Cloudflare's product. Rational, and on schedule. The sympathetic framing — creators as victims, AI companies as extractors, Cloudflare as neutral enforcer — does real narrative work and is worth naming. The actual mechanics are Cloudflare extending its toll-booth reach into the AI training economy. Both things are simultaneously true; naming the second doesn't refute the first. Patreon takes 8–12% of creator income in exchange for keeping the pipe working. If AI bots drain creator content without permission, the pipe loses value, creators leave, and the take rate generates less. The scraping defense fits that business logic cleanly. The robots.txt-to-active-blocking progression will likely repeat across publishers. Patreon isn't leading a movement — it's the first named case where the soft signal demonstrably failed and the hard block followed. Others will run the same calculation. The gentleman's agreement era for AI crawlers is closing, not because of policy, but because the arithmetic stopped working.

• 
  The Don (@TheDon4242) reported 30 minutes ago

  @TeamViewer_help Thnx. This is not new to me. Problem /w reCAPTCHA is that if my environment is out of norm, it will keep me stuck in the loop for 10-15 tries before letting me go through. A pain for paid TeamViewer customer. Consider something sensible like hCaptcha or Cloudflare turnstile?

• 
  Lord Bean (@lifeisameeme) reported 31 minutes ago

  Found the scraping library that makes BeautifulSoup look like it's running in slow motion. Scrapling parses 5,000 nested HTML elements in 1.98ms. Parsel and Scrapy do it in about the same time. BeautifulSoup variants take 1,500ms+. That's not a typo — three orders of magnitude. But speed isn't even the best part. It auto-adapts when a site's HTML structure changes: instead of your selectors breaking silently, it relocates the same element by similarity and keeps working. It also ships stealth fetchers that get through Cloudflare Turnstile, a full crawling/spider mode with checkpoint-resume, and an MCP server so your coding agent can scrape directly. 69k+ stars, 92% test coverage, actively shipping (latest release was days ago). If you've ever had a scraper break because a class name changed, this is the fix you didn't know you needed.

• 
  mico (@0x0_mico) reported 33 minutes ago

  @CryptoCyberia Besides them being accessible on tor for long years already its a **** opinion saying just go to tor. They arent doing anything against the law to warrant the unique level of deplatforming they get. Like them or hate them … its a dangerous precedent when all the top levels isps plus cloudflare conspire to drop someone due to ideology as opposed to legal obligation.

• 
  Katewerk (@katewerk) reported 34 minutes ago

  @Cloudflare The absolute shitshow that is @Cloudflare AI Support: Agent I'm truly sorry for the frustration and the runaround. Here's where things stand and what I recommend: What I've confirmed on your account: No active subscriptions, no zones, no outstanding balances The AI Gateway billing system still has your Visa (ending xxxx) locked as its default payment method — this is a backend issue that cannot be resolved through the dashboard or API You've already submitted two support cases that haven't been acted on Since you've already filed cases and gotten no response, here's what I recommend: Check your existing cases — Go to Support Home and look for "My Cases" to see the status of the two cases you already submitted. If they show as open but unanswered, add a comment to both referencing the AI Gateway billing lock as the root cause. File a new case with a precise subject line — On the Support page, look for any option to submit a new case (it may appear as a button or form, not a tile). Use this as the subject: Payment method locked by AI Gateway billing — cannot remove card or close accountAnd this as the body: I have no active subscriptions, no zones, and no outstanding balances. My Visa ending in xxxx is still locked as the default payment method in the AI Gateway billing system, which prevents me from removing it. I've already deleted the AI Gateway spending limit and auto top-up config. I've submitted two previous cases with no response. I need the payment method detached from AI Gateway billing so I can remove my card and close my account. If the dashboard gives you no way to file a new case, post directly in the Cloudflare Community under the Billing category with the same description. Cloudflare staff monitor billing-related community posts and can escalate them internally. I know this isn't the fast resolution you deserve after already being patient. The core issue is that the AI Gateway billing system has a lock on your card that only Cloudflare's internal billing team can remove — no dashboard or API path exists to clear it yourself.

• 
  shams (@AMR_SHAMS07) reported 36 minutes ago

  @KhafraDev @Cloudflare They do have this, we had backups for R2 but the recovery path was not working at somepoint of failure, that we had to move into garage(self hosted they don’t have object locking yet) but will do the trick

• 
  Ramon 🎹 (@ramonpiano_) reported 38 minutes ago

  the apple signing stuff worked, so i guess lumakeys is an official app now :) well - i still gotta test it on my other mac tomorrow when im back home, but since earlier tests didnt make any problems i expect it to instantly work now i'm trying to finalize some simple onboarding and add update functionality + cloudflare r2 to host the updates i will send out some beta versions to test tomorrow, i already wrote some of you down, but please let me know if you wanna beta test. would love to hear your thoughts and feedback! and then, i guess from tomorrow things are getting real :)

• 
  Paul Jump (@paulljump) reported 38 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 My worst nightmare

• 
  David Escobar (@dbescky) reported 40 minutes ago

  @natmiletic Astro is mostly html and css. So it can render super fast because Cloudflare can cache it and you can make it super lean….. my site speed is sub 1 second on slow mobile. Sub 0.5 on slow desktop.

• 
  Emiliano Blasco (FLG) (@Blascotico) reported 43 minutes ago

  @OnceHuman_ @GearUP_Global It's free, secure, speedy, and backed by a huge company. I'd rather use Cloudflare than pay for the same thing with no real company or support behind it.

• 
  Adam Dawood (@adamdawood) reported 47 minutes ago

  website is stupidly fast as well. never really used cloudflare workers before even though i have been a customer since 2012 when in my first week as PM at @darazpk we were hit with DDOS attacks and @blackmodjo and @Cloudflare rescued us.

• 
  Bassam Nouh (@BassamDahabra) reported 47 minutes ago

  You Have an Idea. This Free AI Tool Tells You Exactly Where to Start: Where do you actually start with AI? Type your idea, pick your skill level, and this free tool gives you a blunt 5-step plan to ship the first version in one week — one step per day, one path, no "it depends." In this video I build the whole thing from scratch and ship it live: the UI, the AI planning engine, the bug that made every plan generic (and the fix), and the free deploy. If you're a beginner wondering how to start building with AI: the answer in this video is — pick ONE idea, pick ONE tool for your skill level, and ship the smallest real version in 5 days. The tool decides those steps for you. WHAT I USED · One HTML file (no framework) — Claude for the build · An LLM planning engine behind a locked-down system prompt · Cloudflare Workers (free) to keep the API key off the page · MailerLite for the email-me-my-plan step.

• 
  Ajay Sohmshetty (@AjaySohmshetty) reported 48 minutes ago

  For context- Cloudflare’s durable execution platform, Workflows, originally only charged for underlying Worker usage, which is CPU-time based rather than clock-time based. In fact, we picked Cloudflare for this exact reason: most of our workflows involve waiting (ex. polling, waiting for network requests to come back), so it was far cheaper for us to use Cloudflare than @temporalio or @inngest for instance. These other durable execution platforms also charge based on “steps” - which I always thought was dumb, because it disincentivizes the best practice of decomposing workflows into small units of work in the form of steps. But unfortunately it seems Cloudflare is following suit, without warning… Feeling blindsided after we’ve already fully built all of our durable workflows on Cloudflare

• 
  Nick Dodd (@nickdodd) reported 51 minutes ago

  @CherryJimbo @Cloudflare @CloudflareDev Pretty terrible looking. Super bland, way too much whitespace (or black space)

• 
  Keith C Wenzel (@keith_c3529) reported 51 minutes ago

  Never be desperate enough to buy tickets through @StubHub or @axs ….one of the worst customer experiences ever. You would be incorrect to think all those extra fees have gone into a good customer experience or a mobile application that actually works. Their inability to staff and manage their @Cloudflare leaves them inept at servicing customer access to their paid for tickets. Instead they force you to jump through hoops, stand in lines and waste your time at an event since they refuse to fix their stuff or hire competent employees who know how to properly configure their cloudflare. Pathetic.

• 
  Glenn 'devalias' Grant (@_devalias) reported 53 minutes ago

  @nickgraynews @computefinx The help docs also mention D1 and R2, which are Cloudflare things

• 
  Alpernoth (@Alpernoth) reported 57 minutes ago

  This website has some serious issues with Cloudflare bullshit, and I'm getting really ******* sick of it.

• 
  CSMurthy (@srism) reported 1 hour ago

  @kav_kavi11 Checking the timeout configurations on your reverse proxy (e.g., Nginx, Cloudflare) or load balancer (e.g., AWS ALB) helps you instantly verify whether the traffic spike is triggering slow responses that break the gateway's current timeout threshold. So B is the correct answer