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:

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 8 minutes ago

  your moat just became someone's weekend project. Cloudflare rebuilt Next.js in five days for $1,100. One engineer. 94% API coverage. MIT licensed. The question Roritharr asked on Hacker News six weeks ago stopped being theoretical the moment vinext shipped: if your backend is trivial enough for an LLM to implement, what value are you providing? we have been calling this a "technical moat" for fifteen years. it was never about the code. it was about friction. as long as cloning your stack took six engineers and a year, competitors did not bother. AI brought that cost down to the price of a used MacBook and a week of compute. the hard part was never the lines of code. the hard part was the negative space. the bugs that live in complex interactions between layers, the stuff nobody wrote a test for. that still costs time. but the reproduction friction that protected 80% of what you thought was your edge? gone. this is not about open source licenses or lawyers. it is about what happens on Monday morning when a motivated competitor with $1,100 in API credits decides your backend is worth rebuilding. i build and ship daily with Claude Code. SaaS, tools, automations. ⭐ if AI can build it, I've probably broken it first. what works → link in bio

• 
  rahul (@ErRahul337) reported 9 minutes ago

  🚨 Another Bad News 🚨 Cloudflare lays off 1,100 employees globally.

• 
  Gabe (@gabebusto) reported 10 minutes ago

  bro setting up an agent to do production work is so easy. you just need to create an account somewhere for your agent to work remotely. cloudflare, hetzner, aws, digital ocean, etc. then pick the agentic tool, and the model, and get an api key or use oauth. then make sure in it's in a sandbox setup with the right permissions and access to your tooling like github, slack, linear, and maybe even some staging and production resources. you really need to be careful though because if agents have any write access to important stuff, it could do something really dumb like delete your database. also for the love of GOD backup your database frequently somewhere the agent can't touch. also prompt injections online can get your agent to leak sensitive env vars so you need to be careful about that. maybe limit network access or inject tokens/sensitive vars once requests leave the sandbox. you probably don't want the agent always on sitting idle, so either figure out how to give it work efficiently to always keep it busy or use some that can pause and resume with ease so you're not billed around the clock for idle resource usage. then you want guardrails in your codebase and deployment pipeline so the agent can't break things and you don't need to feel guilty not reviewing its code. because cmon, nobody wants to do that. you need to make sure your agents have as close to perfect context as possible. so maybe start building a knowledge base, move docs into the repo, or make sure your agent can easily search linear and slack and other places to build context for tasks to work on. and before each task, spend ~10-20+ mins typing things up and giving the agent as much context as possible. oh yeah and your agent ideally should be able to test its changes as completely as possible. so make sure the agent can start up the service(s) it's working on and test them. maybe you need it to open and run a browser, send screenshots, record a video, and so on of its test so you can easily review it in the PR. you also want a bugbot setup in github (if you're still using github at this point) to help scan each PR for potential issues the agent missed. and the agent should be able to automatically address any bugbot findings, fix them, run more tests, and push those changes, and run in a loop until no more bugs are found by the bugbot. i forgot to mention, you probably don't want your agent's code just yolo shipping into **** with no guards in place _after_ it deploys. allow the agent to setup it's new features and code behind feature gates or experiments and do a gradual rollout in case there are any catastrophic problems. then you'll want automatic rollback if issues are detected. and there's probably stuff i'm forgetting, but you get what i'm saying right? it's really not that hard. then you need constant vigilance of your codebase and create lots of skills to help deslop work the agents are doing, maybe create an anti-entropy agent (_another_ agent!) to hunt for growing complexity and auto-create PRs to try and fight to reduce the size and complexity of the codebase. then you'll inevitably have incidents caused by code written by agents that was never reviewed by humans, and either you or yet-another-agent will take a look at your production systems to help you figure out what's wrong because it's all becoming a bit more foreign to you. and you can just have the agent try to make changes on your behalf to fix things and hope to God that it doesn't make things worse. if all of this isn't exciting enough, you then give each engineer and even non-tech team members their own access to the ai tools and agents and models of their choice which easily costs an extra few hundred dollars per month per employee at best. in the worst case, you have someone on the team blow through the team's monthly AI spend by a significant margin by accident using the best models in fast mode because they were too impatient to just use the sota models at normal speed. and spend will likely only go up btw. and if you're not reading between the lines here, product work slows because everyone is playing with agents to learn how to use the agents more efficiently in the hopes that it's a magical bullet that solves all of the woes in software engineering and building production systems. and now you need this magical bullet to work because you're falling behind to teams who maybe aren't distracted spending all this time and money trying to make this all work. but you're definitely going to catch them. once you've figured this out, you'll 10x or 100x your output and leave them in the dust! or... you could just have engineers start coding by hand again before it's too late and becomes a lost art. you can even make modest and tasteful use of ai, but without doing all of the above. i actually miss the days of supermaven and early cursor. they were so simple and actually removed some friction and some of the annoying parts of coding.

• 
  Raj Vardhman (@Mr_rajvardhman) reported 17 minutes ago

  @Cloudflare We’ve already paid and settled the invoice, but our services are still down. This is impacting our operations. Please resolve this urgently.

• 
  QUEST.py (@victorokolie_) reported 21 minutes ago

  Actually yes, using Cloudflare can help a lot, especially for static content and smarter routing. But if your web app is mostly dynamic, it won’t completely remove latency from physical distance. For most projects, latency is still manageable on a single Hetzner VPS unless you’re building something realtime-sensitive. If needed, use Cloudflare CDN + caching + Argo before paying for another server

• 
  Rachel Gilchrist (@rachelgilchrist) reported 23 minutes ago

  @IndeedSupport @indeed I can't get your site to load thanks to the stupid cloudflare loop. When I try to report it the link takes me to the cloudflare loop again. How am I supposed to report access issues if I can't even access the site?!

• 
  XenoBlock (@MonyetSipit) reported 28 minutes ago

  Is cloudflare workers down? #WorkersDown

• 
  Alpheios | Trades (@TheWiseAdapter) reported 29 minutes ago

  Adobe $ADBE & Cloudflare $NET both down on earnings lastnight. Again, we might see a small pivot back to #AI ? $MU strong in premarket. I dont like that they are sharing liquidity... it shouldnt have to be dog eat dog.. but..it is Grabbed some $RKLB on good results lastnight.

• 
  Matt Convente (@mattconvente) reported 33 minutes ago

  @mil000 **** this. Annoying CAPTCHAs, Cloudflare “verification”, press and hold, and now this.

• 
  Ankit Jaiswal (@itsankitjaiswal) reported 35 minutes ago

  Cloudflare just laid off 1,100 people. That's 20% of their entire company. Not performance issues. Not cost-cutting. Their exact words: "agentic AI-first operating model." AI agents are now doing the jobs. The humans got the memo. These were the jobs everyone said were safe.

• 
  2WBIA (@2WBIA_Reformed) reported 38 minutes ago

  @gelbooru @Cloudflare As part of Cloudfare TOS they can terminate your service of they feel like it lol eat ****

• 
  Duckitis(アヒルの乳首) (@lxn_ni) reported 39 minutes ago

  @baileyjay161521 Cloudflare gay as ****, why would he pay for higher streaming costs for the off season to at best 500, watch on kick

• 
  Timothy Schneider (@tschenanigans) reported 39 minutes ago

  I have had a bunch of people reach out to me at the end of this week about @Cloudflare and they have all asked me one thing Do you really use that much AI at work? Yes. Yes I do. I personally think the power of AI, here specifically, is how much I have been able to learn. 600% growth in AI usage. I would argue my growth has been 600% as well. And it may sound corny, but holy ****. I've learned more about more than I would have ever before. I have learned real implementations I built along the way. I have been able to set up, troubleshoot, repair, and fix known processes and bugs, sure. I think more importantly I've been able to create! I've been able to take an idea...and stop wondering if it would work. I didn't spend hours poring over documents and trial and error. I spent hours developing and creating and iterating on failed processes because AI helped me un-fail them. If a customer needed anything from things I already had a great understanding for (WAF, DNS, Gateway) to things I had zero clue on where to even start (a simple Snippet, Worker, DB migrations thanks to @CloudflareDev) I was able to respond to them. The amount of "I'll get back to you" and "I'm not really sure" gaps in time have shrunk. But so have the amount of times you have to say it. That is growth. I have a pretty deep understanding I feel on a few different things, but I know more about @Cloudflare because I can spend hours consuming and then actively questioning that knowledge. I rant a bunch, but if I can leave anyone with anything regarding AI: Build skills, that build skills.

• 
  Evan Liu (@evan123liu) reported 40 minutes ago

  The software quality is really trending down. Right after Canvas got hacked Discord is also down. Last year there was also a bunch of issues with AWS and Cloudflare. Plus, the amount of bugs on Apple's iOS or MacOS also significantly increased in recent years. I wonder if this is due to the increasing prevelance of vibecoding that caused so many software developes to not even check the code before they ship into production...

• 
  BLANPLAN | 空界計劃 (@blanplan) reported 42 minutes ago

  @_its_not_real_ Let's Encrypt halt + CloudFlare + Discord simultaneous outage suggests something deeper than typical infra hiccup. SSL cert chain compromise scenarios always seem unlikely until they happen, and the timing alignment is concerning. Worst case: a CA-level compromise, in which case half the internet's trust model resets in 48 hours.