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:

• 
  Tremis Wealth Tracker (@tremisai) reported 4 minutes ago

  Cloudflare just posted record revenue — $640M, beat every estimate. Then cut 1,100 jobs. 20% of the company. In one day. Why? AI usage up 600% in 3 months. The machines replaced them. Stock down 24%. Record revenue. Record layoffs. Welcome to the AI economy. #NET #AI #Cloudflare

• 
  baleyg (@aldagutr) reported 5 minutes ago

  I still need to track down some cheaper hard drives because I’m about to start hoarding massive amounts of videos. I'm also ditching Nginx for Cloudflare.

• 
  Gabe (@gabebusto) reported 6 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.

• 
  Stan Tscherenkow (@stantscherenkow) reported 9 minutes ago

  Cloudflare cut 1,100 jobs at record revenue. Internal AI usage went up 600% in three months. The CEO did not call it a layoff. He called it the "agentic AI era." Translation: the work some of those people were doing is now done by something that does not get tired, ask for a raise, or take vacation. If your company is still arguing whether AI affects headcount, you are reading the wrong book. The ones who already moved are not announcing it. They are quietly cutting and reinvesting. The hire who is not shipping in three months when AI does in three days is not a hire problem. You hired against a job that no longer exists.

• 
  Fred Velez (@Fredvelezcrypto) reported 10 minutes ago

  Crypto people spent years talking about disruption. Now disruption is showing up in the HR department. Coinbase reportedly cut around 14% of its workforce. Cloudflare announced cuts around 20%. AI layoffs are not theory anymore. They’re showing up in real org charts. And the uncomfortable truth is simple: AI is not coming for “jobs” first. It is coming for tasks. Research. Writing. Support. Coding. Marketing. Analysis. Admin work. A lot of jobs are really just bundles of repeatable tasks. And AI is getting faster, cheaper, and better at those tasks every month. Some companies will use AI intelligently. Some will use it as a convenient excuse to cut costs. Either way, the worker has to adapt. The future is not humans vs AI. It is humans using AI… against humans who refuse to learn it. Brutal? Yes. But markets don’t care about comfort. They care about efficiency.

• 
  Brandon Marin (@joanbadiavalls) reported 11 minutes ago

  $NET Cloudflare had a nice 3x beat, but the stock is down by nearly 20% after hours. The stock has been priced beyond perfection, but hopefully this marks a shift to a more reasonable valuation where I can buy it. They also announced a layoff of around 20% of their workforce, alluding to part of the reason being AI. "Cloudflare's usage of AI has increased by more than 600% in the last three months alone."

• 
  Timothy Schneider (@tschenanigans) reported 12 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.

• 
  Akash (@roguesherlock) reported 14 minutes ago

  @RhysSullivan @kr0der I don’t understand what exactly do people enjoy about cloudflare workers tbh. Like what is it that’s not available and/or better on other platforms? I understand if it’s durable objects but workers I just don’t get, I’ve always had some issues with it. I’d only use it as a global switch / router, even then I see weird latency spikes

• 
  Scott (@scottstts) reported 15 minutes ago

  Cloudflare downsizing by 1100 employees, claiming AI as the reason, and stock goes down by 25% in a day Used to be the exact opposite There’s a clear narrative change happening just recently it seems Part of it is because using AI as a shield for layoff when clearly it’s not because of AI is backfiring But I think also part of it is the realization that using AI to do more is the way to go, and using AI to cut cost is not This is true both in a practical sense and also aspirationally

• 
  rahul (@ErRahul337) reported 18 minutes ago

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

• 
  ToochiDennis (@ToochukwuDennis) reported 25 minutes ago

  Stopping the bad guys with Cloudflare: 535 malicious requests blocked or challenged in the last month #cloudflare

• 
  The Future Is The Past (@FuturePast138) reported 27 minutes ago

  @Pirat_Nation Cloudflare sucked, crashed the internet, made companies lose billions, and now of course "it's because of AI we are laying off people, it's not because our product is bad" 🤡

• 
  Kiro (@KiroIkigai) reported 32 minutes ago

  Cloudflare $NET just: ✅ Beat EPS ($0.25 vs $0.23E) ✅ Beat revenue ($640M, +34% YoY) ✅ Raised full-year guidance Then fired 1,100 people. 20% of the company. CEO memo: "This is not a cost-cutting exercise." Their AI usage went up 600% in 3 months. Employees run thousands of AI agent sessions every day engineering, HR, finance, marketing. Every department. The AI productivity thesis is coming to fruition Stock down -18%. But the math underneath is clear fewer people, same output, expanding margins. Full-year EPS guidance RAISED to $1.19-$1.20 vs $1.14 expected. Unit labor costs just printed 2.3% vs 4.5% expected yesterday. Wages growing 0.2% vs 0.3% expected this morning. Productivity running above its long-term trend for years. You are not bullish enough.

• 
  Justin Bennett (@just_be_dev) reported 32 minutes ago

  Is @Cloudflare broken on firefox for anyone else?

• 
  Just a Dude Who Invests (@DudeWhoInvests) reported 35 minutes ago

  GOD DAMN Cloudflare $NET getting dragged through the mud stomped on, spat on, jumped on, dragged through the mud again, and thrown off a cliff?!??? Erased a fourth of their market cap today. 😮