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:

• 
  Karl Emil Nikka (@KarlEmilNikka) reported 7 minutes ago

  @Cloudflare Nice! Do you have any ETA for sub-domain support?

• 
  Court Reinland (@Court_Reinland) reported 8 minutes ago

  @EddCoates Cloudflare can help with this, they can tune out a lot of this.

• 
  Patrick St. Jean (@stjeanp) reported 8 minutes ago

  @EddCoates I dealt with some of the same stuff, ended up putting them behind Cloudflare proxies, which helped somewhat. The biggest fix was blocking specific ASNs. Specifically AS132203.

• 
  Sameer Khan (@sameerr_dev) reported 10 minutes ago

  Every API you've ever used has a limit. Tweet too fast? 429. Hit GitHub's API in a loop? 429. Spam a login page? 429. That's a rate limiter doing its job. But here's the thing - I never really understood what was happening *under the hood* until I started digging into it. So what exactly is a rate limiter? Simply put: it's a system that controls how many requests a client can make in a given time window. Why does it exist? - Protects your server from being overwhelmed - Prevents abuse (scrapers, bots, brute force) - Ensures fair usage across all users - Saves you money (compute isn't free) - Keeps your service alive when traffic spikes Without it, one bad actor (or one buggy client) can bring your entire system down. You've probably seen the response headers: X-RateLimit-Limit: 100 X-RateLimit-Remaining: 43 X-RateLimit-Reset: 1716300000 That's the rate limiter talking to you - telling you how many requests you have left and when the window resets. Where do rate limiters actually live? - At the API Gateway level (before requests even hit your server) - In middleware (Express, Fastify, etc.) - At the CDN edge (Cloudflare, AWS CloudFront) - Inside the application itself This is just the beginning. In the next posts, I'm going to break down all the major algorithms used to actually implement rate limiting with real code, not just theory. Follow along if you want the full series.

• 
  Shantun Singh Parmar (@ParmarShantun) reported 12 minutes ago

  @uday_devops For which they gave always coupon you can use them, also thier support is quick not like GoDaddy and cloudflare charge

• 
  IJav (@javmung) reported 12 minutes ago

  @MSU_NW_FANG @MaplestoryU @nexpacetime Also need to test WARP From CLoudflare.. that helps a lot. But most likely is his/her ISP. mine was disconencting a lot, they did reset my NAT, and assigned me a public IP address, and problems are gone.. so routing probably the problem.

• 
  Turac (@TuracTheThinker) reported 19 minutes ago

  Deploy plane decoupled: Arcane GitOps, HA GitOps, Cloudflare Pages. Agent never touches what it changes.

• 
  63green (@63green) reported 21 minutes ago

  So @Cloudflare works overtime to destroy thei reputation by sending emails despite every notification turned off, and I’m willing to grant their request to never, ever trust this criminal company, and never use them. Any company willing to **** you by email will **** your data.

• 
  Jeff Needles (@jsneedles) reported 22 minutes ago

  @Hussain_Joe @_ceifa Well, the key is its pretty much managed, just not e2e. Like it's Cloudflare Workers + pipelines + queues -> CH cloud. All managed services! Just the raw volume makes most "pure" managed analytics providers extremely prohibitive -- like prob 10x the cost at least. Of course, there's other options that are really self hosted that are less analytics-focused... or things that rely more on object storage as the source of truth (like R2 SQL, which would actually prob be cheaper) But I've put in maybe 10 hours of necessary maitenance in the last year, occasionally the analyst who uses the system will ping me for questions/advice etc -- but raw infra/system wise, like 0 issues!

• 
  Pushkar Mishra (@Pushkarm029) reported 24 minutes ago

  Just install Cloudflare WARP. No login. One click solution. No ads.

• 
  Brandon Bedford (@wealthpotion) reported 24 minutes ago

  "Claude is down" is the new "Cloudflare is down" except way worse.

• 
  Jorge (@tebayoso) reported 26 minutes ago

  I had my @cloudflare bill spin up from 0 to 500 per day, and their interface was broken for two days, when I noticed I had to pay 900usd. They don't respond to customer support :(

• 
  Hermann (@dhlotter) reported 31 minutes ago

  Cloudflare Pages said Active. CLI said Active. URL returned old content. Pages uses 'Active' to mean the deployment slot is live, not that the latest commit finished building. My 'fix' sat undetected in the build queue for two days. Watch the stage statuses. #cloudflarepages

• 
  Vatsal Mishra (@cryptikcell) reported 35 minutes ago

  Dead Internet Theory is aging annoyingly well. Cloudflare says agentic AI bots now generate 57.4% of global web requests, compared to 42.6% from humans. But “bot” is too broad. Some bots crawl, index and monitor the web. Others spam, impersonate and poison the data loop. The problem is provenance. The future internet needs to answer one boring question really well: who or what created this?

• 
  GangGangHODL 💎🙌 (@GANGGANGHODL1) reported 36 minutes ago

  Problem: generating image variants on Heroku is ruby-vips memory intensive, causing R14 memory quota exceeded Solution: Cloudflare Image Transformations processing Offload Image compute & memory req from Heroku worker to Cloudflare worker Why: deliver sm images to mobile