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:

• 
  Cassiel (@Cassiel1137) reported 3 minutes ago

  @SportingNest @Cloudflare Quite spectacularly a scam. Luckily anyone who might fall for it (cough... everyone has their off days fella... cough) wouldn't have the first clue how to do any of that ****.

• 
  Nuvorlane (@nuvorlane) reported 7 minutes ago

  Cloudflare AI Gateway monthly usage invoices no longer break out input and output tokens. Previously you got two lines, e.g. 40k input at $0.000001 ($0.04) and 24k output at $0.000005 ($0.12). Now one line: anthropic/claude-haiku-4.5 — $0.16. Model names on invoices and logs also normalize to provider/model, so dated suffixes disappear from the identifier. Credit-purchase invoices are unchanged. If a FinOps parser keys on token line items or version suffixes, fix it before the next month-start invoice lands.

• 
  William Bello (@belljobs94) reported 9 minutes ago

  THE GOAT on their free service !! @Cloudflare hands down

• 
  Noel Ceta (@noelcetaSEO) reported 11 minutes ago

  8/ Layer 5: CDN implementation (distribute content): CDN = Content Delivery Network How it works: - Content stored on multiple servers worldwide - User gets content from nearest server - Fast delivery regardless of geography Setup: - Cloudflare (easiest, free tier available) - Akamai (enterprise) - CloudFront (AWS) Impact: 20-40% speed improvement for global sites.

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 15 minutes ago

  AI-generated Rivet Actors / Workflows are (finally) here 🥂 Some design notes on Dynamic Apps: Powered by agentOS → provides lightweight sandbox-as-a-library V8 isolate runtime → generated apps scale to 0, cold starts in ms, 22 MB per app, native JS performance (not slower WebAssembly like QuickJS) Novel Node.js-compatible runtime → ground truth agents already know & existing libraries work, native performance No nested virtualization → pure userspace, like Chromium & Cloudflare Workers Self-hostable → Dynamic Apps can run anywhere, including Kubernetes, Railway, EC2, etc (which don't support microVM / KVM) SQLite sharded by actor → scalable, fast, cheap, uses no compute when idle A Rivet namespace per app → isolates its actors, separates billing, and nothing to provision Builds run inside agentOS → npm install & build steps in the WASM sandbox, like a Dockerfile without the Linux VM Dynamic Apps also supports plain REST backends & static frontends deploy the same way

• 
  pkuseri (🍉) (@Pkuseri_) reported 19 minutes ago

  @stupidtechtakes Do you know any better alternatives aside cloudflare? Not being rude or anything if the tone sounds rude mb

• 
  Adam Rackis (@AdamRackis) reported 20 minutes ago

  @kettanaito @flydotio Do your pods auto-sleep when they’re not getting traffic? I think there’s a min setting you have to set to zero to let everything shut down and then just cold start on the next request. Really though surely Cloudflare free tier is simpler?

• 
  R.Gion (Any/All) (@Gion_the_critic) reported 21 minutes ago

  @SportingNest @Cloudflare Where was this? I've never seen it

• 
  James (@jamescoder12) reported 22 minutes ago

  The full impact. What he changed and what happened: 1. Moved router from cabinet to open shelf: 74 Mbps → 155 Mbps 2. Changed Wi-Fi channel to least congested: 155 Mbps → 290 Mbps 3. Widened channel width to 80 MHz: 290 Mbps → 380 Mbps 4. Switched DNS to Cloudflare (1.1.1.1): browsing latency dropped noticeably on every device 5. Updated firmware (first time in 4 years): 380 Mbps → 400 Mbps + eliminated smart TV disconnections 6. Changed admin password + upgraded to WPA3: closed the 2 biggest security holes in the network 7. Separated 2.4 GHz and 5 GHz bands: eliminated TV buffering caused by band steering 8. Enabled QoS (work laptop prioritized): zero Zoom call drops during peak household usage 9. Bought own router, returned ISP rental: $168/year saved + full control over all settings Starting speed: 74 Mbps (on a 500 Mbps plan getting 15% of what he paid for) Ending speed: 440 Mbps (getting 88% of what he paid for) Then the real move: he downgraded from the 500 Mbps plan back to 200 Mbps because 200 Mbps with optimized settings delivered faster Wi-Fi to his devices than 500 Mbps with factory defaults. Monthly savings from the plan downgrade: $30 Monthly savings from returning the rental: $14 Total annual savings: $528 with faster, more stable, more secure internet Total time to make all 9 changes: 15 minutes of settings + one trip to Best Buy + one phone call to return the rental.

• 
  Blockchain Daily News (@blckchaindaily) reported 23 minutes ago

  🚨 CLOUDFLARE $NET EXPANDS AI AGENT SUPPORT, NOW RUNS CURSOR CLOUD AGENTS ON CLOUDFLARE SANDBOXES FOR CUSTOMER-CONTROLLED EXECUTION - PRESS RELEASE

• 
  Jean Suze (@JeanSuze8) reported 24 minutes ago

  @Navlio @Lovable Cloudflare wasn’t the original cause. The initial issue happened before Cloudflare was added: mysite was unreachable from several Belgian networks, while it worked perfectly through a VPN and from abroad. DNS, TCP 443 and TLS were all fine, and another site of mine on the exact same hosting IP worked normally from the same connection. We only added Cloudflare later as a workaround. The redirect loop that appeared afterwards was a separate issue: my app still had an old hardcoded mysite → www.mysite redirect, while Lovable was redirecting www.mysite → mysite because the apex domain was set as primary. That created the infinite loop. That part is now understood and fixable. What we still don’t understand is the original Belgium-only outage. Nothing in the DNS/TLS tests explains why the hostname stopped returning HTTP responses from Belgian IPs but worked immediately over VPN. That’s the part we’re still waiting for Lovable to explain.

• 
  Utsav Patel 🇮🇳 (@mr_utsav_patel) reported 25 minutes ago

  @Cloudflare @CloudflareHelp @Yank if you could help here...

• 
  Krishna Singh (@krishnasinghdev) reported 27 minutes ago

  @tapasadhikary @Namecheap I never liked namecheap / godaddy, don't know why people choose it over simple providers like cloudflare where they charge same amount for 1 or 10 years

• 
  JK (@_junaidkhalid1) reported 33 minutes ago

  @dillon_mulroy @EffectTS_ the cloudflare support point is the one that actually moved me. a lot of these framework bets fall apart the moment you try to deploy somewhere real. effect holding up there changes the calculus.

• 
  Austin (@IamAroke) reported 34 minutes ago

  @nickstewart_ Cloudflare went down because of a regex. That's not a joke, that actually happened.