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:

• 
  Jean Suze (@JeanSuze8) reported 47 seconds 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.

• 
  Villainess of Resevoi (@GalCharoShipper) reported 1 minute ago

  @Tepafray @Sean_Topic AI crawlers simply ignore ****. Even layered defenses recommended by artist-protection groups (Glaze for image-level noise, Cloudflare-style bot blocking, watermarking, opt-out registries) are described as a partial, constantly-shifting arms race, not a solved problem

• 
  Kevin Minnelli (@minnelli) reported 3 minutes ago

  WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

• 
  COLLINSEO (@alexcollinseo) reported 4 minutes ago

  Breaking news! Your site might start blocking AIs from September 15th.. And if you block them, you won't show up in AI answers. The good thing? It takes a sec to unblock! This setting is inside Cloudflare. You might not even know your website uses Cloudflare because it works in the background as a CDN, helping your website load faster. If you check your website using the tools I mention, you can find out whether Cloudflare is being used on your site. Cloudflare seems to have taken this step because of how AI companies are crawling websites, and honestly, I don't completely disagree with the reason behind it. But having AI crawlers automatically blocked from September 15 could be a problem if you want your business to appear in AI answers. The setting is inside Security Settings. Look for the AI crawler control and make sure it is set to allow rather than block. This is especially important if AI visibility is part of your strategy. With one of my clients, we went from zero to around 500 visitors from AI traffic in two months. And what I did was exactly what I explained in the video. If your AI crawlers are blocked, you're potentially closing the door on that traffic before it even has a chance to reach you. #SEO #DigitalMarketing 👇🏼 Comment VIDEO for the FULL VIDEO BREAKDOWN

• 
  Austin (@IamAroke) reported 5 minutes ago

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

• 
  That Brazilian Omo Eko (@sholawa) reported 6 minutes ago

  Cloudflare has my airtel IP restricted lol.... Slow internet caused it; I must have hit the rate limit that day...

• 
  JK (@_junaidkhalid1) reported 8 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.

• 
  Mikael Pawlo (@mpawlo) reported 10 minutes ago

  @stutireal cloudflare is never down - I would blame the dog

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 12 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

• 
  Patrick Ryall (@PadraigOraghail) reported 15 minutes ago

  The learning is never ending. Mostly it is platforms, in this case using Cloudflare as the auth gate. I had never used cloudflare for more than DNS. Now I have three sites running on it, for free, which is mad. Workers, Zero Trust, DNS, connected to ***. It's all rather slick.

• 
  James (@jamescoder12) reported 16 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.

• 
  Tang Vu (@tangvu_dev) reported 18 minutes ago

  In the Vietnam 100-VU burst, Cloudflare averaged 191.77 ms vs Vercel’s 430.95 ms. P95 was 337.11 vs 879.96 ms, with 0% errors on both. But cross-region burst tests reversed the winner in the same regions as the warm tests.

• 
  Reyansh Bahl (@reyanshbahl) reported 21 minutes ago

  @wongmjane @Cloudflare One of the big issues I had with the current worker previews was not being able to deploy durable objects per preview, hope this fixes it

• 
  Kene 🐘 (@spatocodex) reported 22 minutes ago

  @acolombiadev @Cloudflare Not just generous, Cloudflare is so good. A service you can gladly pay for.

• 
  Go₿rrr.me (@GoBrrr_me) reported 22 minutes ago

  @janrothen @paoloardoino @The_Pi_Hole And/or set your DNS Servers to: Primary: 1.1.1.2 Secondary: 1.0.0.2 Cloudflare blocks a lot of bad stuff like phishing, scams, and malicious domains right at the network level.