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:

• 
  CAPED CRUSADER🦇 (@stilleclectic) reported 3 minutes ago

  @matthansbello Sigh, everything was originally done on namecheap but I’ve now just moved the dns to cloudflare. Waiting to see if that fixes the issue

• 
  Adrian Fritz (@adrianwjfritz) reported 4 minutes ago

  5/ Governments and major tech companies are already moving. Most blockchains are catching up. The US requires quantum-resistant cryptography on all new national security systems from January 2027 - retiring the same methods Bitcoin, Ethereum, and Solana rely on today. Cloudflare, Apple, Signal, Microsoft, and AWS are already deploying upgrades. 24 of the top 26 blockchain protocols still rely entirely on methods being phased out elsewhere.

• 
  rita kozlov 🐀 (@ritakozlov) reported 5 minutes ago

  at a lot of companies, product's role is to come up with ideas, carefully groom the roadmap and narrowly define requirements for engineering to (blindly) follow this maybe makes for an "easier" product role but limits creativity (and accounrability) one thing that's unique about cloudflare is that ideas can really come from so many more places product's role is to help map those ideas to customer problems and make sure we actually solve them and help get those ideas in customers' hands (aka actually ship it and make it good!) it makes for a much more interesting role and breeds so much innovation and leads to better experiences because engineering is not exempt from taking ownership in the deliverable. "i shippped what's in the PRD" is not good enough. you own the customer problems & solutions together

• 
  The Vibe Coder (@quantumaidev) reported 6 minutes ago

  Cloudflare works by sitting close to users. Requests can be cached, filtered, routed, or blocked at edge locations before reaching the origin server. It protects and accelerates by moving decisions nearer to the network boundary.

• 
  firtoz (@firtoz) reported 7 minutes ago

  @EddCoates Would/does Cloudflare help?

• 
  Your Private Proxy (@YourPrivateProx) reported 8 minutes ago

  AI agents don't know they're blocked. Cloudflare returns 200 with a JS challenge. Agent sees no data, retries, gets the same 200, loops for 20 minutes. Not a model problem. Missing check: is this response actually data, or is it a block page?

• 
  Malte Landwehr (@MalteLandwehr) reported 8 minutes ago

  @EddCoates So many solutions: · Cloudflare/CDN · Caching · Free API without authentication I once worked for a website with 90% bot traffic. This issue is manageable.

• 
  George Apostolakis (@Apostolakis_Geo) reported 10 minutes ago

  @YashHustle_22 I used netlify for small projects in the past until I realised that it sucks so I switched to cloudflare

• 
  Pieces by Julian Undav (@piecebyjulian) reported 11 minutes ago

  I also understand that some of the words on pallets changed. PLEASE NOTE THAT the words were minted onchain, so your words are safe! We shifted the hosting site to Cloudflare after so many api calls (why the site was down for a couple of days) Please bear with us. working hard right now

• 
  The AI Entrepreneur (@ai_in_it) reported 12 minutes ago

  the big AI labs trained on most of the public web. now a ton of those same sites are locked down tight. cloudflare, login walls, bot checks you basically have to pay to clear.

• 
  ∱ (@Fallibilist) reported 12 minutes ago

  @ni5arga Yeah, not working on network DNS, cloudflare works

• 
  Richard Illingworth (@RCIllingworth) reported 16 minutes ago

  manually setting up 1,000 cold email inboxes takes 40+ hours of straight clicking. i just built a workflow in Claude Code that replaces it: a LOT of guides on this skip the things that actually trip you up. • there's a Porkbun bulk-DNS bug that quietly skips records on bulk update. • a forwarding-box behaviour that strips your DNS on a misclick. • a Cloudflare nameserver gotcha that yanks resolution off your records the second you tweak anything on the origin host. • and there's a missing TXT propagation check that hides for 48 hours. hit ANY one of those and your accounts fail. you'll only notice 3 days in when a client emails saying "none of these are sending." same mistake i've watched cold email guys make over the last 2 years, so i put together an asset that will solve this for GOOD. inside the video: 1. the exact bulk setup workflow that replaces 40+ hours of manual clicking 2. the Porkbun bulk-DNS QA pass we run after every bulk update to catch missing records 3. bulk-update DNS gotchas you'll only hit at scale 4. the Cloudflare nameserver gotcha and what to check on your origin host before it pulls resolution 5. the manual-vs-automated breakdown so you know whether to film this for your own team or run it yourself if you want it... • comment "ACCOUNTS" • follow me so i can DM you the video ps. if you've been quoted 40+ hours for an inbox build, that's someone else's slow workflow.

• 
  Steve Brownlie (@sdbrownlie) reported 16 minutes ago

  @asaio87 For some things I found it more annoying than opus lol. I'm sure it was smarter - it realised some bug I was trying to solve was actually a cloudflare temporary/transient issue and it was right it went away by morning. gpt-5.5 didn't think to check that... but... other than that i agree it wasn't very different.

• 
  Sreram Rathnam (மோடியின் குடும்பம்) (@sreramrathnam) reported 16 minutes ago

  Bro, let's understand how server infrastructure and network security policies actually work. If someone tries to flood a website with over a million artificial hits using automated bots or scripts, the Hosting Server Provider and Cloudflare would immediately flag it as a malicious volumetric attack, suspend the URL, or ban the site entirely to protect hardware resources. However, the website has been completely active and up for almost a week without a single second of downtime. This is because Cloudflare Edge Servers have thoroughly cross-verified all incoming concurrent traffic using unique IP addresses and request headers, authenticating it as human traffic. If it were automated bot traffic, Cloudflare's built-in Automated Bot Management system would have instantly mitigated and blocked it at the network layer before it even registered on the telemetry dashboard. Basic server provider policies and network protocols confirm that this volume is fully validated, bro.

• 
  TheLarioso (@TheLarioso) reported 17 minutes ago

  @brivael You have these massive scripts CloudFlare many are connected to and collect ip:s and check if bots etc. - you could very well just go ip and block those that exist - yes, quite a few but can be done I think You do not need to go to a particular service, you vpn service has an ip.