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:

• 
  primitive.host (@PrimitiveHost) reported 4 minutes ago

  Anyone else using @Cloudflare "Email Address Obfuscation" feature having crawl issues on @ahrefs crawler? It detected /cdn-cgi/l/email-protection on ALL my pages and ate up my entire crawl limit for the month 😶

• 
  pathik (@pathikghugare) reported 5 minutes ago

  @NotRoodraksh @4k_isn not working on cloudflare warp

• 
  Coffee and Gun Oil (@coffee_oil) reported 6 minutes ago

  @ShamashAran I was on cloudflare ******* with DNS last night. I hate DNS The **** I run locally works fine, but that's because it's me and a text file.

• 
  simulx4 (@simulx4) reported 7 minutes ago

  cloudflare is using Kimi K2.6 to automatically resolve billing issues. and... it worked fine. it fixed my problem faster than any human. by chat/email... so much better than talking to a person, honestly

• 
  Glitch Truth (@glitchtruth) reported 8 minutes ago

  Day 28 of 30. 30 Days of Practical Tech. A reverse proxy is a server that sits in front of your real server. Cloudflare runs one for free in front of millions of sites. Visitors hit Cloudflare's IP never yours so attackers can't find your machine. Tomorrow Day 29: what a CDN actually is.

• 
  Edd Coates | Game UI Database 2.0 (@EddCoates) reported 14 minutes ago

  @mishuba Damn, it's almost as if I have a robots.txt *and* cloudflare, and it's still happening. That's WILD, huh? And no, I didn't vibe code my website, i'm not a cretin.

• 
  Nicholas Preston (@Mike_Preston17) reported 15 minutes ago

  @PLOwingPots @DevLeaderCa You really should learn C and C++ to understand the fundamentals, etc. I say this as a C# dev who went C -> C++ -> Java -> C#. You won't appreciate the 'better' language nearly as much if you don't at least suffer from the shortcomings of its successor language. I suffered pointer and stack overflows from C++ and that taught me to not be an idiot with my memory. Rust babies devs too much, imo - that's what (again, imo) led to the Cloudflare outage: too much trust in the compiler and willfully ignoring the dynamic nature of data in production (which NO language can account for).

• 
  Adrian Fritz (@adrianwjfritz) reported 16 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.

• 
  KarenR (@heykarenrc) reported 19 minutes ago

  When I built d1-studio, I was still early in my transition from UX to development. At first, I just wanted the simplest stack possible. Something lean. Something affordable. Something I could build with fast. Like many new devs, I started with the familiar stack: Next.js. Supabase. Vercel. AI helping me along the way. Supabase was great to get started. I still like it. But as I built more products, I started noticing the small costs and tradeoffs that you only understand after shipping. Storage. Egress. Deployment limits. The usual “newbie learns the hard way” stuff. That pushed me to look for a stack that fit how I wanted to build. Then I found Cloudflare. Workers. Pages. D1. R2. Queues. Generous free tier. Simple deployment. Close to the edge. I slowly moved more of my projects there and never really looked back. But there was one thing that kept slowing me down: Cloudflare D1 local development. D1 is great, but working with the database locally felt too slow. I didn’t want to keep jumping between CLI commands just to inspect tables, edit rows, run SQL, or check data while building. I also didn’t want a tool that required a long setup. My thinking was simple: The database is already in my Cloudflare project. The wrangler.toml is already there. Why can’t a studio just detect it and work? That became the trigger for D1 Studio. A native database studio for Cloudflare D1. No complicated setup. No extra database connection string. No heavy workflow. Just run it inside your project and start working with your D1 database faster. You can inspect tables, edit data, run SQL, and work with local or remote D1 without fighting the CLI every few minutes. It started as a tool I needed for myself. Now it’s getting used by other Cloudflare developers too. This week it hit 311 weekly downloads. Not a huge number in the grand scheme of things, but for me it means a lot. Because this is the first product I built that truly came from my own pain. Not a random idea. Not a trend. Not something I forced. Just a problem I kept hitting until I finally built the tool I wished existed. That’s been the biggest lesson for me as I move from design into development: The best products are often not born from brainstorming. They come from friction. Something feels slower than it should. Something takes too many steps. Something breaks your flow. And eventually you think: “There has to be a better way.” That’s how D1 Studio started. And seeing people use it for their own Cloudflare projects is still one of the best feelings.

• 
  JustAnotherUser_4 (@JAU_4) reported 21 minutes ago

  @EddCoates Cloudflare firewall, thank me later. I blocked entire countries. Solved so many problems.

• 
  Curtis Thornton Jr (@RdclslyGudLookN) reported 23 minutes ago

  @EddCoates Of course cloudflare could never stop my automated scrapers, and now they're offering automated browsers that aren't even as good as mine, perhaps reasoning that they know what they can stop and can always choose to not stop themselves.

• 
  Headmaster Duck (@HeadmasterDuck) reported 23 minutes ago

  @specialkdelslay First thing, put a free cloudflare account in front of this, see how much their basic bot mitigation helps. Next, if you don't mind throwing $20/mo at the CF pro plan, this is a mostly solved problem between their super bot fighter and ability to issue challenge requests from the predictable regions of the globe. If $20/mo isn't in the cards, you can keep blocking IPs and also look into blocking by certain headers and user agents.

• 
  Bernardo Gonzalez (@bgonzalesp) reported 25 minutes ago

  @CloudflareHelp @Cloudflare how do you expect we can contact support to gain access to my account, if you require to login to send a help request??? It's simple logic... I assume that your really don't care about helping your customers

• 
  Diogo D (@DiogoTheReal) reported 25 minutes ago

  @EddCoates @Cloudflare rate limiting might help

• 
  JD (@TooTrill4Thiss) reported 27 minutes ago

  @BoringBiz_ Every business doesn't need a custom agent. It needs an enterprise plan and a few capable devs who can map it, and deploy agents. building automation that don't rely on agent compute. like hello??? app scripts, compute engine, cloudflare workers. ******** are people doing?