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:

• 
  Big-Abdul (@BigAbdulWeb3) reported 4 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Jacob Bartlett (@jacobtechtavern) reported 5 minutes ago

  @eastdakota @Cloudflare Hold on, I think I've got the hang of this now. I haven't read it, but when they say "building for the future," are they announcing a massive layoff?

• 
  John Thilén (@JohnThilen) reported 7 minutes ago

  @jakebarlo @CloudflareDev @rauchg Cloudflare has a good track record. They keep a sizable portion of the Internet reasonably secure. The track record of Vercel is at most reactive. They fix stuff when others complain.

• 
  artee (@artee_49) reported 8 minutes ago

  cloudflare is down 16% after hours

• 
  Devicetocloud (@devicetocloud) reported 9 minutes ago

  @eastdakota @Cloudflare Damn, really sad day. As a cloudflare customer, your team has been good for me.

• 
  S. K. (@i_hate_intel) reported 9 minutes ago

  @jmdagdelen Cloudflare and coinbase did it because of bad earnings. That's it. The others: maybe.

• 
  josh (@JoshCaughtFire) reported 10 minutes ago

  @stupidtechtakes Technically, the issue is it’s exposing internal header names added by Cloudflare and maybe LBs not sent by the original client. Doesn’t look like a real issue since it’s basically leaking you use CF which is obvious from response headers anyway, but it does technically leak infra details from

• 
  toks (@toksdotdev) reported 12 minutes ago

  really sucks to hear about the cloudflare layoff. lots of really great folks there.

• 
  BlackIntus (@Blackintus) reported 14 minutes ago

  Cloudflare $NET just cut 20% of its workforce because AI replaced parts of the workflow. The stock still fell 19% — because Wall Street now wants AI profits, not AI headlines. 1/ Cloudflare just fired 20% of its workforce. Not because revenue collapsed. Not because growth disappeared. Revenue grew 34%. They did it because AI changed how the company operates. 2/ The market reaction? Cloudflare stock crashed 19%. That tells you investors are starting to fear something much bigger than layoffs: AI may be compressing the value of human labor faster than companies can monetize it. 3/ Cloudflare employees increased AI-tool usage by over 600% in one quarter. That is not adoption. That is an operational transformation happening in real time. 4/ Read the language carefully: “This is not a cost-cutting exercise.” Translation: The company believes fewer humans will permanently be needed to run high-growth software businesses. 5/ More than 1,100 jobs eliminated. At the same time: • revenue beats • earnings beats • guidance beats This is the new AI economy. Companies can grow while shrinking headcount aggressively. 6/ Coinbase cut 14%. $COIN Block cut thousands. $XYZ Upwork cut 24%. $UPWK Bill Holdings cut 30%. $BILL The pattern is becoming impossible to ignore. AI is no longer “assisting” white-collar work. It is replacing layers of it. 7/ Cloudflare’s management openly said they are redesigning the company for the “agentic AI era.” That phrase matters. AI agents are moving beyond chatbots into autonomous execution. Research. Coding. Customer support. Operations. Finance workflows. Entire org charts are now under pressure. 8/ And investors are conflicted. In some companies, layoffs boost the stock. This time the market punished Cloudflare hard. Why? Because Wall Street is starting to ask whether AI productivity gains also destroy future software hiring growth itself. 9/ For 15 years, SaaS valuations depended on one assumption: More growth = more employees = bigger companies. AI breaks that model completely. The next generation of $100B companies may employ a fraction of the people older tech giants needed. 10/ This is the real AI disruption story. Not image generators. Not viral demos. The restructuring of the global white-collar workforce. And it’s accelerating faster than most executives expected. Are you realizing AI is already replacing thousands of high-paying tech jobs? What happens if companies cutting staff for AI become Wall Street’s new normal? Follow @blackintus. We track where labor markets, capital, and AI collide first.

• 
  Just a Dude Who Invests (@DudeWhoInvests) reported 16 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. 😮

• 
  Kevin Milan (@KevinDewanSr) reported 17 minutes ago

  选题：Cloudflare裁员1,100人，股价暴跌18%——AI正在吃掉自己的生态 1. This just hit my radar and it's brutal. Cloudflare (NET) just fired 1,100 people after earnings. The stock tanked 18%. But the real story is why they did it. AI is replacing their own engineering teams from the inside out. I've been saying this for months: the first wave of AI job displacement is not hitting factory workers. It's hitting $200K234. Let me put a number on this fear. 1,100 engineers at Cloudflare averaged maybe $180K56. My read: NET stock will recover because the market rewards cost-cutting. But the signal here is bigger than one stock. We just watched a $30 billion company prove that AI can replace its own builders. The question for every tech worker is no longer "will AI take my job?" It's "am I already training my replacement?"

• 
  Vincent Po Li (@Vincent_Po_Li) reported 21 minutes ago

  @levelsio AWS egress: $80/TB. Hetzner: $0. the bandwidth tax is the silent line item most indie SaaS founders never compare until year 3. hetzner plus cloudflare in front equal the unbeatable solo-builder stack

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

• 
  Al-ameen (@alameenpd) reported 25 minutes ago

  @Cloudflare support is basically non existent

• 
  Gus (@guscsales) reported 26 minutes ago

  Hmm, the problem actually was on my mobile, for some reason the cloudflare tunnel wasn't updating, now I see in the computer and actually it's exactly as I asked