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:

• 
  rusa (@rusabuilds) reported 6 minutes ago

  @dhh @OpenAI @Cloudflare the part that took the work there is owning the trust root. a distro repo means you sign, you decide what lands, and you carry the revocation story. the aur was never bad at delivery, it was bad at saying who vouched for it.

• 
  Artyom Shimanski (@a_shimanski) reported 8 minutes ago

  @truehannan @Cloudflare never got why people pay for vercel

• 
  RJ Finnegan (@1rjfinnegan) reported 8 minutes ago

  If your project isn't on @cloudflare, you're seriously missing out on not only huge savings but also flexibility. I used to think it was a benefit to have multiple vendors, which it is for some use cases, but Cloudflare honestly simplifies a lot of the infra for most applications. Plus, if Cloudflare ever goes down like it did last year, 80% of the other websites are also down 🤷

• 
  Tittiecoin (@Tittiecoin_) reported 9 minutes ago

  I have been cooking and have updated @Cloudflare. We have a bunch of @Tittiecoin_ updates and sites that support solana:CMmMKQJZbRFBAfUM3mraXaVyEjjTMWUtBaUcSEDGpump almost ready to release, as well as our Official #TittiCoin Community on @telegram. Do not say I haven't given you enough time to grab a bag and HODEL! CA: CMmMKQJZbRFBAfUM3mraXaVyEjjTMWUtBaUcSEDGpump

• 
  Nifal Adam (@nifal_adam) reported 14 minutes ago

  @PhilcMay @a_shimanski @Cloudflare Durable objects have one big problem, its stateful. So if it gets stuck you are in for a surprise bill. So best to use it responsibly.

• 
  Alex Greenland (@ajrgd) reported 17 minutes ago

  cloudflare could never

• 
  Ashley Peacock (@ashleypeacock) reported 20 minutes ago

  I don’t use a VPS at all, shut it down long ago in favour of hosting everything on Cloudflare These days, the developer platform has everything you could need to host 99% of apps (For transparency: I work at Cloudflare but I’ve built on them for way longer than I’ve worked for them)

• 
  Edeb (@_Edeb) reported 21 minutes ago

  @Majora__Z @p_e_t_e_r_s_e_n Cloudflare’s Sept 15 change is bigger than it looks. They’re flipping the default: AI training crawlers get blocked on any page that shows ads, and multi-purpose bots like Googlebot (which still does both search indexing and training data collection in one) get caught in the same net unless the site owner manually opts out. That means a huge chunk of the web — especially free-tier and new sites on Cloudflare — could suddenly stop letting Google crawl them. Implications in plain terms: Google’s index starts going blind on large parts of the internet. Search results get thinner, older, and more reliant on whatever they already have cached or on AI summaries that never send traffic back. Publishers finally get real leverage. They can protect their content from being vacuumed up to train models that compete with them, without (in theory) fully disappearing from search — but only if they carefully configure the settings. Most won’t. A lot of smaller sites will just let the default ride and vanish from Google. Users will notice it slowly: more “no good results,” more AI answers that feel hollow, more content locked behind logins or paywalls because free crawling no longer makes economic sense. The open web’s old deal is dying. For thirty years the bargain was “crawl everything for free and send traffic back.” That deal is broken. Cloudflare is forcing the next phase: either separate your crawlers cleanly, pay for access, or get locked out. It’s not the end of the internet. It’s the end of the free-for-all version of it.

• 
  Hamid Siddiqui (@hamidInventions) reported 21 minutes ago

  @wickedguro @markgalkev tbh now not 100% sure if it might be the same reason since you mentioned everyone getting this same time but i strongly feel it would be Cloudflare only, I faced this issue few months back. When i was debugging this I disabled Cloudflare proxy for a while and tested posting the posts that were failing to post on TikTok, and they worked fine. I also used to face similar issue with fal.i/replicate where they would randomly fail to get the R2 image url i passed for image generation. It was fixed as well. The exact steps i took I don't recall, would have to check what settings i did change eventually.

• 
  VC Intern (@the_vc_intern) reported 23 minutes ago

  Cloudflare is not shutting down Google Search on September 15. It is forcing Google to decide what Googlebot actually is. Cloudflare’s new controls divide crawlers into three jobs: Search, Training and Agent. Search remains allowed by default. Training and Agent traffic will be blocked on ad-supported pages for new sites and existing free customers that keep the new defaults. A crawler doing multiple jobs inherits the strictest rule. That puts Googlebot in an awkward position. Cloudflare classifies it as both Search and Training. A publisher that welcomes search indexing but rejects AI training can therefore block the entire bot. For years, bundling those jobs gave Google leverage. Publishers depended on search traffic, so refusing the crawler also meant disappearing from discovery. Cloudflare is moving that decision from a line in robots.txt to enforcement at its network edge. Google now has three choices: separate its crawlers, convince publishers to permit both uses, or lose access to pages that still want search traffic but no longer accept training as part of the bargain. The web is not dying here. Its access contract is being renegotiated. Robots.txt was a request. Cloudflare is turning it into a gate.

• 
  Hajnen Payson (@hajnen) reported 23 minutes ago

  Everyone thinks AI layoffs are just about replacing coders and copywriters. Look closer at the restructuring at Amazon, Cloudflare, and Block. They aren't just replacing tasks. They are eliminating "The Coordinator." For decades, corporate structures needed middle managers because compiling reports and passing information between departments was slow and expensive. AI now does that instantly. But there is a massive trap hiding in these new "flat" org charts: If a company cuts headcount first, but fails to redesign its legacy approval processes—the remaining employees are completely screwed. You inherit the exact same meetings, the same performance expectations, and the same corporate bureaucracy... just with fewer colleagues to help you do it. Cutting heads without redesigning the workflow isn't an "AI Transformation." It's just a recipe for burning out your top performers. Source article by @DocHutcheson

• 
  Jubilance - Off Record (@luftraptorAD) reported 26 minutes ago

  @bathotek @Raafkoning @iyici_ It’s a recent issue, the scrapper has had AI folded into it since 2024 and that’s what Cloudflare is hoping to force Google to split off from the main crawler.

• 
  Dwinity (@dwinity_eco) reported 27 minutes ago

  @signalapp @Cloudflare the math was never the weak part. the key directory was. every e2e messenger asks you to trust a server handing out keys, and apple shipped contact key verification in ios 17.2 for exactly that. verification you have to remember to do is verification nobody does.

• 
  Sean Finnerty (@sean_infinnerty) reported 29 minutes ago

  @jpschroeder @dschewchenko someone from @Cloudflare recently posted on X that spend limits were actively being worked and would be shipped soon. Better late than never

• 
  perdrix (@perdrix_fl) reported 31 minutes ago

  @glenngabe Another HUGE item for AdSense publishers is that @Cloudflare blocks Google’s access to ads.txt by default… I learned that one the hard way and it would be such an easy fix for Cloudflare to make.