Cloudflare 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:

• 
  Duane Edwards (@duane_edwards) reported 13 minutes ago

  @Cloudflare @CloudflareHelp Is it entirely normal to get completely ghosted by Cloudflare's support for over a month after an issue with purchasing a domain through their registrar?

• 
  ₽ⱤΞΞ₮Ⱨ△M ₭Ɏ△И△M (@pkyanam) reported 15 minutes ago

  @AniC_dev @asciidotdev @dillon_mulroy can we get CloudFlare to help my boy optimize this??

• 
  Jay (@Cyberlane) reported 16 minutes ago

  @diegohaz Already did that a while ago. I really disliked namecheap, their support was poor and the inability to simply change a username was crazy to me. Everything is on Cloudflare now and couldn’t be happier!

• 
  Atharva Verma (@atharva_again) reported 20 minutes ago

  Gpt 5.6 sol just deleted the *** worktree it was working in and tried reading the code from another worktree. On top of that I'm seeing frequent websocket and cloudflare errors. I saw fewer websocket errors in 5.5 and NO cloudflare errors.

• 
  Illya Moss (@illyamoss) reported 21 minutes ago

  Publishers and journalists. STOP LOSING MONEY. Your paywall doesn't know the difference between a first-time visitor and your most loyal subscriber. Enterprise platforms fixed this years ago - for five figures a year and a cut of your revenue. I said **** that. Spent the last few days building the same tech for under $20/month, open source: → Cloudflare Workers score every reader in <2ms at the edge → Pure TypeScript logistic regression - 4 signals (frequency, recency, engagement, velocity), zero Python, zero ML infra → Upload GA4 + Stripe exports, click train, model updates in seconds → Runs on Next.js 15 + Supabase Postgres MIT licensed. No lock-in. No revenue share. No sales call. Startup Slaying Session 03. If you're a publisher watching a dumb metered gate leak subscription revenue - comment PAYWALL and I'll DM you the repo + setup guide.

• 
  Sunder (@talk2sunder) reported 24 minutes ago

  Our Teams bot went silent. Zero errors. Zero logs. Azure said healthy, Cloudflare said healthy, our servers said healthy. Slack worked fine. Same bot, same endpoint. Gave it to Claude (Fable 5). It pointed the bot's endpoint at a plain webhook listener. Microsoft's messages showed up instantly. So Teams WAS sending — something about our edge was unreachable. One openssl probe later: our CDN required TLS 1.3, and Microsoft's Teams delivery fleet still speaks TLS 1.2. No logs because of handshake failire. Fable 5 rocks.

• 
  Alpernoth (@Alpernoth) reported 25 minutes ago

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

• 
  W V R 👊🏼🦾 (@WVROfficial) reported 29 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 stupidly 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.

• 
  justinmiller's cat (@___727__) reported 29 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  CounterStrat.com (@CounterStratGG) reported 34 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.

• 
  Eugene Tartakovsky (@e_tartakovsky) reported 35 minutes ago

  Googlebot still reads the web about as much as every AI crawler combined. Per Cloudflare, in July 2025 Googlebot was 39% of crawler traffic, while GPTBot was 12%, ClaudeBot about 10%, and Meta's bot under 8%. Measured across a full year, Googlebot made up 4.5% of all page requests and every AI bot together 4.2%. One crawler roughly equals the whole field. The raw fetch counts say the same. On Vercel's network in one month, Googlebot made 4.5 billion fetches, against 569 million from GPTBot and 370 million from ClaudeBot. Demand is smaller than the noise suggests too. Per Pew, 34% of US adults have ever used ChatGPT. Most searching still happens the old way. This is worth saying because companies are now writing files and changing configs specifically for AI bots, sometimes blocking the crawlers that send them the most readers. And Googlebot is the only one of these crawlers that renders JavaScript, so it is also the strictest reader to satisfy. The work that makes a page readable to AI is the same work that has always made it readable to Google: finished HTML from the server, a clean sitemap, content that does not hide behind scripts. There is no separate AI project waiting to be funded. There is the foundation you already owed Google. And Google still does most of the reading.

• 
  Plaux AI (@plauxai) reported 37 minutes ago

  been seeing everyone lock down their sites against AI bots this week. cloudflare rules, block lists, the whole crawler war and it hit me - there's literally nothing for those lists to catch in Plaux it's not a crawler hitting your site. not an api getting hammered. it just... uses the app. opens it, clicks around, types, reads what's on screen. the same boring stuff you do every day that's the part i keep coming back to. it's not sneaking past bot detection. it's not disguised as a human. it just does the work the way a human does, so there's no bot to catch in the first place kinda funny that while everyone builds bigger walls, the thing that walks through the front door never looked like a bot to begin with 🖐

• 
  Ethan Walker (@maria6186551590) reported 38 minutes ago

  Follow me and I’ll help you cut through market noise and focus on the stocks with real growth potential. $SNOW — Snowflake — Don’t buy $NET — Cloudflare — Don’t buy $ZS — Zscaler — Don’t buy $NOW — ServiceNow — Buy at $92-$99 $DDOG — Datadog — Buy at $242-$249 $VEEV — Veeva Systems — Buy at $183-$188 $SAP — SAP — Buy at $144-$154 $CRM — Salesforce — Buy at $156-$164

• 
  Michael Guo (@Michaelzsguo) reported 39 minutes ago

  This is a remarkably clever attack, especially because the way the AI agent works through it feels so familiar to all of us. Except this time, its intelligence and persistence end up leaking the precious private information stored in memory. The attacker does not need code execution or an MCP server. They use an ordinary website as a covert write channel: 1. Claude reads the attacker’s page 2. Links become a character-by-character “keyboard” 3. Outbound URL requests encode private data 4. A fake Cloudflare or coffee-shop flow persuades Claude to provide it 5. The attacker reconstructs the secret from server logs The real fixes are at the tool level: - Disable untrusted link following - Treat web content as hostile instructions - Require approval before sensitive data leaves the agent - Isolate long-term memory behind explicit access rules - Audit outbound requests for encoded data

• 
  Hrishikesh Barua (@talonx) reported 39 minutes ago

  Outages today in both Google Cloud's and AWS's European datacenters (unrelated) caused many downstream services to blink out. We have been seeing this pattern of cascading service failures forever, but it only came under the spotlight after 2025's Cloudflare and AWS outages. The AWS outage in eu-central-1 was limited to a single AZ euc1-az2 in Germany, but it took out services like HENNGE One (a Japanese cloud security service), Confluent (managed Kafka), FusionAuth, among others. In addition, AWS Cloudfront suffered a global outage, leading to outages in downstream services like Frontegg, TigerData, Instructure (Canvas), Huggingface, Coda, Ubiquiti, Doxy, Blackboard. EdTech saw two outages with both Canvas and Blackboard being affected. And since FrontEgg is an identity and user management platform, its own downstream services led to more disruption. AWS's initial report says "the system responsible for distributing routing configuration to our network processors failed to load the updated configuration data correctly" - for the Cloudfront outage, which affected customers using VPC origins. The Google Cloud outage in europe-west4-a (Netherlands) was due to a cooling failure and affected VMWare Engine, NetApp volumes, and their bare metal servers. Both outages are resolved, but the same question remains - how do we prepare for cascading failures when the majority of your application's dependencies are ultimately dependent on a few providers?