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:

• 
  Manas Tripathi (@tripathigrows) reported 5 minutes ago

  Cloudflare replaced NGINX over its process model, not its code. Per worker pools fragment at scale, so origins eat endless handshakes. Pingora shares one pool and pushed a customer from 87.1 to 99.92 percent reuse. Rewrite when the architecture is the ceiling.

• 
  Zahid (@epiczahid47) reported 7 minutes ago

  i wish cloudflare had a postgres service, thats the only thing rn thats holding me from going full cloudflare stack. sometimes d1 isn't enough. (trying to self host umami)

• 
  Shayan Nadeem (@shayannadeem123) reported 8 minutes ago

  @Taniyatweets_ GitHub but most website servers are behind cloudflare if that goes half of internet will go down.

• 
  Sinan🌍 v2 (@sinanisler) reported 12 minutes ago

  @ClaudiuSararu @BraydenWilmoth comparing cloudflare dash to google ads is criminal i would never do that :D

• 
  MasterBismuth (@MasterBismuth) reported 13 minutes ago

  ****'s sake. Just managed to get my account unlocked because now my Firefox on my desktop can't seem to pass the stupid ******* Cloudflare challenges I'm constantly inundated with. Gonna lock my account but I doubt it'll help. Nikita Bier left this site in a dogshit state.

• 
  Ax🕸️ (@wireheaded) reported 15 minutes ago

  @naoufal_elh @mauruschatm @bot Use those Starlink IPs if you have to, to get around cloudflare & google's IP blocks. Change the search engine if google captcha issue can't be resolved for search.

• 
  Javed (@jshai0) reported 19 minutes ago

  The final result: • 27.5M+ stored OHLCV rows • 122,960 Parquet objects • 13,154 chart artifacts • Cloudflare-native daily updates • A small API read path • No provider call for every chart request We stored the data because repeated API calls were the problem. We built the API on top of our own data because predictable reads were the goal.

• 
  Tobias_Petry.sql (@tobias_petry) reported 20 minutes ago

  @scheemunai @shanejones The number of people disabling scripts is neglible, mostly non-existent. The bigger problem will be adblockers blocking the Google Analytics code. So your real number I guess will be say like ~20% higher than GA reports. The Cloudflare one is highly inflated all the time.

• 
  Pramod Gupta (@pramodhq) reported 21 minutes ago

  Tried to renew my domain today. GoDaddy showed ~$16.70/year. At checkout: ~$27.20 before tax. I thought it was a bug. Turns out ~$10.50 “Full Domain Protection” had been added. I tried turning it off. The entire domain disappeared from the cart. So instead of renewing, I transferred the domain to @Cloudflare Cost: ~$10.46 +1 year included New expiry: 2027 A ~$10.50 upsell turned a renewal into a lost customer. Interesting way to do retention.

• 
  Maciej Nowak (@mnowak_eth) reported 24 minutes ago

  Cloudflare does not cache your HTML by default. You can be paying for Cloudflare and still have none of your HTML cached there. Would you be able to tell this is your case? By default Cloudflare caches by file extension, not by content type. CSS, JS, images: yes. The HTML document, the thing PHP and the database assemble: not by default. Without an explicit rule, every page view still goes to the origin. I have seen more than one setup where "we have a CDN" meant the logo loads from the edge of the network and everything else works exactly as before. Check the cf-cache-status header. If an HTML document comes back as DYNAMIC, the edge is not caching it at all. What I also hear on calls sometimes are two words traded as if they were two products: CDN and edge. They are not two products. It is the same few hundred machines Cloudflare keeps around the world, and the two names come from different decades. CDN says what the thing does, deliver content. Edge says where it is located, at the far end of the network. For twenty years those were words for the same servers, and then the industry started using edge for the code you can run on them. Nobody planned that, so it is not on you if the two names blur together. What is different is not the name but the job you give those machines. Handing out copies of files, your images, CSS and JS, comes with the account. No decisions, it's just simple distribution, working from the moment you point your domain at them. The other job is running your logic up there: assembling and caching whole HTML pages, telling a logged-in visitor from an anonymous one, holding the product page while letting the basket through untouched. It's not on by default because it needs rules: what may be stored, for whom, for how long, and what wipes it. And you are the one who knows those rules. And the principle that ties this whole series together: cache layers are a cascade, not a set of independent switches. The lower layers have to hit before anything propagates up and reaches the edge. Getting that order right is messy work, and it is the reason a site feels smooth when someone has done it. So before you add another layer, you should be able to say three things about it in plain words. What it stores: files, whole pages, or answers from the database. Who is allowed to get the same copy: everyone, or does a logged-in visitor need their own. And what removes that copy when the content changes, plus who is able to trigger it. If any of the three is a shrug, you probably have something messed up and don't know it yet. We created a great guide to understanding caching specifically for WordPress. Link in comment

• 
  Mehul Mohan (@mehulmpt) reported 27 minutes ago

  youtube is not going down every week because ai video slop is accelerating? cloudflare is not going down every week with so much bot traffic increase? i used to feel for github because of massive AI workload spike they have to handle, but it has been a while now. they had more than enough time now. this is a pure management, attention to detail, or talent issue at this point over github. disappointing

• 
  Brown Geeky kid (@shigma_male) reported 30 minutes ago

  YouTube isn’t going down every week because AI video slop is increasing. Cloudflare isn’t collapsing every week because bot traffic is rising. I used to give GitHub the benefit of the doubt because AI workloads created a massive traffic spike. But it has been long enough now.

• 
  iddqd (@iddqd_usa) reported 31 minutes ago

  @liran_tal I don't really get it. Surely if your org thinks it can go through the complexity of enforcing this through cloudflare it's easier to enforce without using CF? A lot of CF products sound cool but maybe I am missing something, their target customer is who exactly...

• 
  Dylan Garcia (@_dylanga) reported 32 minutes ago

  @VicVijayakumar @Cloudflare I'm 100% sure that if my instance were to go down right now I would have no clue how to get it back up and running. I was looking at my deployments notes from back then and it involves deprecated docker-machine, a docker network on the host, etc. Just a pain. Cya!

• 
  Pranjal Paliwal (@betterclever) reported 32 minutes ago

  you can tell a good software engineer apart today by their current advocacy of @Cloudflare primitives and how much they use them to decompose problems in agent native world. literally a litmus test