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.

• Domains (40%)
• Cloud Services (34%)
• Hosting (20%)
• Web Tools (4%)
• E-mail (2%)

Live Outage Map

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

City	Problem Type	Report Time
Greater Noida	Cloud Services	3 hours ago
Colima	Hosting	2 days ago
Leuven	Domains	2 days ago
New Delhi	Cloud Services	3 days ago
Mâcon	Cloud Services	8 days ago
Ashburn	Domains	12 days 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:

• 
  Timur Gok (@timatbyteful) reported 8 minutes ago

  Browser Use published a proper 2026 web scraping guide this week. Worth reading if you're building anything that touches the open web. The stealth benchmark is the most useful part. Across 71 sites protected by Cloudflare, Akamai, PerimeterX, and Datadome, Browser Use Cloud hit 81% success. Browserbase came in at 42%. The gap between providers is not marginal anymore. If you're picking infrastructure based on price alone, that gap shows up quickly in production. The distinction between basic and interactive scraping is also framed well. Basic scraping is increasingly commoditised. The data worth having in 2026 tends to sit behind login walls, search interfaces, and multi-step flows that require actual browser interaction. Browser Use's open source library at 83k GitHub stars suggests developers building serious pipelines have already worked this out. One finding I hadn't thought much about: Cloudflare's Browser Rendering tool intentionally identifies itself as bot traffic. Which means it gets blocked on virtually any protected site. Cheap but limited to targets with no anti-bot at all. The guide also covers where AI fits into the scraping stack. Extraction, code generation, self-healing selectors. Less about replacing the infrastructure layer and more about reducing the maintenance burden on top of it.

• 
  Kevin Luciano (@KELG_12) reported 10 minutes ago

  is cloudflare down?

• 
  REN | Serverless Infrastructure (@ren_assetcolle) reported 13 minutes ago

  Grid bots aren't slow because of bad code. They're slow because of where the code lives. Cloudflare Workers fires from 300+ locations worldwide. Your order reaches the exchange before the SaaS queue even starts.

• 
  Ìlérí⚡️ (@pipe_dev) reported 15 minutes ago

  @ibrahimraimi_ @brimblehq Hi hi, it’s been fixed. Issue was a stale cache from Cloudflare

• 
  Mete (@ymetemert) reported 15 minutes ago

  Has Cloudflare gone down or not???? There is no reliable source, its been 10 minutes and no one has posted an update on the site #Cloudflare aloo

• 
  Narek (@NarekHakobyan) reported 21 minutes ago

  @hiradp @Cloudflare Cloudflare is cool, Cloudflare support is horrible

• 
  Ravi Kishor (@kishorravi21) reported 23 minutes ago

  @Geekbench Linux CLI upload fails (“internal code 35”). Cloudflare returns cf-mitigated: challenge (HTTP 403), which CLI can’t solve. Tested on ISP, hotspot, VPN — same issue. Any fix?

• 
  Irbaaz Kadri (@irbaazkadri) reported 23 minutes ago

  @Cloudflare @CloudflareDev @GoDaddy Even at the end of 1 hour they still can't fix it.

• 
  FilmLadd (@FilmLadd) reported 23 minutes ago

  You're absolutely right about the remote-service issue not being unique to AI, it's a terrible idea for most businesses in most use cases, but everyone still keeps falling for it. It's like mixing the Sirens from Greek Mythology with Groundhog Day. Cloudflare crashing the Internet multiple times all on its own within a few years' time comes to mind.

• 
  Mr. H ☭⃠ (@HenryHi31107817) reported 24 minutes ago

  Imo whenever cloudflare is down they should be locked in the building and unable to leave until they fix it

• 
  John Curtis (@jcurtis) reported 25 minutes ago

  @GTMPugh @problogger Hey just a thought. Great use case for cloudflare durable objects. 1 per person. Basically free for a while, isolated, queryable (as opposed to just r2 object) , scales to zero as far as I know so long lived inactive users don’t slow everything down or get expensive.

• 
  C:/LEGENIUX.EXE 🌐 (@Crazymindplow) reported 26 minutes ago

  @Cloudflare Still waiting for ubiquity to support NAT64 :(

• 
  JaFicht (@JaFicht) reported 27 minutes ago

  When I started building internal tools with AI, security was my biggest worry. I’d run security checks on the code, but I couldn’t honestly say every vibe-coded app was airtight. And every new app expanded my attack surface. Then I set up Cloudflare Zero Trust (free up to 50 users). Now my server isn’t on the public internet at all. The only way in is through a Cloudflare-managed tunnel: sign in with Google, your email gets checked against a whitelist, and only my team gets through. The real win was the mental shift. Instead of securing a dozen apps individually, I secure one gate. Outbound API calls still work fine. Inbound traffic from anyone not on my team simply doesn’t reach the server. I trust Cloudflare + Google a lot more than I trust my vibe coded web apps. If you’re shipping internal tools with AI, this pattern changes everything.

• 
  Michael Andreuzza (@Mike_Andreuzza) reported 29 minutes ago

  @CiprianiRanieri Ahh from lovable. Take it down and deploy to Cloudflare or Hetzner, would make it cheaper. No, I personally think see no value on that, sorry.

• 
  mfg.xbt (@mfg_ip) reported 32 minutes ago

  agents needed a body. Cloudflare is turning browser + network + edge runtime into the default skeleton: run the task, touch the web, move close to the user. the API call was step one. the runtime is the product now.

• 
  vimtor (@vimtor) reported 33 minutes ago

  @hiwinit we had cloudflare support, but it was only halfway there it's my belief that if we have native support for something, it should be really good but don't worry, we are getting closer to most use cases and tomorrow's announcement will be about aws

• 
  Marc-André Moreau (@awakecoding) reported 34 minutes ago

  @Ryan_Hecht If you can have Cloudflare support officialized in the docs that would be absolutely perfect. Ideally tested with instructions to make sure there's no surprise. We already have Cloudflare at work, and it checks a lot of boxes for what I'm looking for

• 
  Orthodox Caveman (@Orth0doxCaveman) reported 36 minutes ago

  @FistedFoucault The problem nowadays is mostly coming from third party providers we didn't need in the past for security, like cloudflare, or payment processors. Developers preemptively put those restrictions in place to avoid having problems later on.

• 
  James Ross (@CherryJimbo) reported 36 minutes ago

  Isn’t this a major breaking change from Cloudflare across every proxied site? There’s lots of api clients that have indiscriminately sent accept: application/json and then had custom html response handling for Cloudflare errors 🤔

• 
  DJ Coastal (@PostalCoastal) reported 36 minutes ago

  @bneeditor Cloudflare is down again...

• 
  Diego E. Solórzano (@diegoesolorzano) reported 37 minutes ago

  @Cloudflare Hey, I had an issue with billing on Apr 7th. Filled a support ticket and still having heard from you. The price on the model's docs page and the price you actually pay are not the same number. In my case the gap was 18x. @CloudflareDev

• 
  Barry Merritt☦ (@barrymerritt) reported 37 minutes ago

  @GeekyBoarders Who DDOSs anymore? It's expensive and takes a lot of resources. The bandwidth required is huge. 500Gbps - 1000Gbps. Major router services like Cloudflare shut it down quick.

• 
  SmartPSX (@smartpsx_pk) reported 46 minutes ago

  @SonOfStockMan Heya. Emails are routed through cloudflare, processed on a private backend server in memory, and once data is extracted they are discarded/trashed immediately. Some might be retained for up to 30 days in case of any error or other issue for debugging, but they're not like accessible directly or anything. Uploading screenshots isn't viable for a few reasons. One is that screenshots aren't as accurate when processed, and second is that every screenshot costs AI processing fee for me. You can always directly upload or share the pdfs you get over mail with the app if you're not comfortable forwarding the email itself 🤔

• 
  Dean Hayes (@HayesDean7246) reported 47 minutes ago

  @DavidDavisMP You need to protect yourself, as a 12 year old script kiddie with access the internet could launch a DDOS attack, it's isn't hard, the service you need is called Cloudflare. Don't worry about the cost, the taxpayer, as always, has broad shoulders....

• 
  Tom W (@TomWinTejas) reported 49 minutes ago

  @TexasAnCap Cloudflare is good if you are close to one of their resolvers. You'll be fine, likely hit theirs in Dallas. But if you're somewhere outside of their footprint they don't support EDNS Client Subnet which has negative impacts on some CDNs. Quad Nine supports EDNS CS and has pretty good POP density as well.

• 
  AlterRion (@AlterRion) reported 50 minutes ago

  @Cloudflare I can't pass the Cloudflare captcha in relatively old browsers anymore from yesterday. Please, fix it.

• 
  Mitchell Bennis (@mitchell_bennis) reported 59 minutes ago

  @prestonjbyrne Curious if an American website that uses a service like Cloudflare, where the site may be cached on overseas servers for faster access, would be considered a foreign presence.

• 
  Ross (@RV_Smirnov) reported 59 minutes ago

  MCP just had its "open redirect" moment — security researchers found prompt injection and tool poisoning flaws. Meanwhile: Google DeepMind adopted it, Cloudflare shipped native support, and enterprises are betting billions on agent infrastructure anyway. The pattern? Build fast, secure later. Same story as APIs, npm, the web. @yoheinakajima @Thom_Wolf @emollick

• 
  Chynen Eide (@chynen_eide) reported 1 hour ago

  I have to admit. Cloudflare is awful. Firstly, security verification: most of the websites get a verification if you are not a bot and that's fine. The problem is that it failed to load (it refreshes over and over and over again) until it started to work. Then if you think that's bad, Some websites get down for like a HOUR.

• 
  Saket Tawde (@SaketCodes) reported 1 hour ago

  Convenience tax, which I actually happily pay for the projects which are on Cloudflare. Plus target audience (for this tool) is folks who are not on AWS for a reason. I mean, I just built a landing page with a registration form the other day, and the best part, didn't have to manage a single secret anywhere in the code or the settings UI, I never left my terminal, thanks to their Bindings. The real value with CF is iteration velocity. Not everyone's cuppa, but definitely well positioned for the eco system we are in.