Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Domains (40%)
• Cloud Services (34%)
• Hosting (19%)
• Web Tools (4%)
• E-mail (2%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Noida	Hosting	3 days ago
Augsburg	Domains	4 days ago
Montataire	Cloud Services	8 days ago
Greater Noida	Cloud Services	10 days ago
Colima	Hosting	12 days ago
Leuven	Domains	12 days ago

Full 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:

• 
  FossilSouthie (@SouthieFromSTW1) reported 4 minutes ago

  NVM Cloudflare is dying. Not an Epic Games issue this time. The cloud has been having issues the whole day today

• 
  Alper FERUDUN (@AlperTheKing) reported 6 minutes ago

  Cloudflare cut 1,100 jobs (20% of workforce) on the same day it reported record Q1 revenue of $639.8M, +34% YoY. CEO Matthew Prince frames it as a re-org for "the agentic AI era," not cost reduction. The cuts hit support, not engineering. 📉 WHAT HAPPENED - 1,100 eliminated, headcount from 5,500 to 4,400. - Stock fell ~24%. - Prince: "not a cost-cutting exercise" but a restructure for the agentic AI era. 👥 WHO GOT CUT - Customer success, technical support, sales-adjacent roles hit hardest. - Engineering largely preserved. 💰 WHY IT IS DIFFERENT - Record $639.8M quarter, +34% YoY, same day as layoffs. - Internal AI usage up ~600% in 3 months on Workers / vibe coding. - This is not margin defense; it is a bet that AI agents are now the primary contact surface. 🐤 THE CANARY - When revenue is at a record and AI usage is at a record and a workforce gets cut, customer support is the role AI hits first. - The hype says AI is coming for engineering jobs. Cloudflare fired the humans engineers built tools to replace. 📋 THE PRECEDENT - Klarna 2024-2025: AI took over 2/3 of inbound chats, support cut, resolution times held. - Salesforce, IBM, Duolingo, Dropbox trimmed support while preserving engineering. 🔮 CLOSING THESIS The canary in the AI coal mine is customer support, not the codebase. The headcount delta between support and engineering at AI-forward companies is the indicator that matters.

• 
  Laurentiu (@Bitheap_tech) reported 7 minutes ago

  @MichaelSwengel @eastdakota @Cloudflare Even with heavy cooking of their books they still didn't manage to beat expectations. Bad company and it's only going to get worse with their clanker obsession.

• 
  infusionvictor (@infusionvictor) reported 12 minutes ago

  Cloudflare beat on earnings. Beat on revenue. Raised full-year guidance. Stock down 19%. Why? Two things. First: Q2 revenue guidance came in just below estimates. By less than $1 million. The market didn't care about the beat. It cared about the miss. Second: they cut 1,100 employees. 20% of the company. The reason: AI usage inside the company surged 600% in three months. They don't need the people anymore. AI creates trillion-dollar companies and eliminates thousands of jobs in the same earnings call. Datadog up 31% on AI growth. Cloudflare down 19% on AI efficiency. Same technology. Opposite outcomes. 📡 Follow the signal, ignore the noise. $NET $DDOG $NVDA $QQQ

• 
  Stock Analysis (@stock_analysisx) reported 12 minutes ago

  Market Bullets 📊 Jobs growth surges past forecasts: The U.S. added 115K jobs in April, down from 185K in March but far surpassing expectations of 55K. Unemployment held steady at 4.3% and wage growth cooled, while job losses for February grew to -156K. Cloudflare cuts workforce: $NET (Cloudflare Inc.) fell 16% premarket after the company announced plans to cut more than 1.1K employees as it shifts to an AI-first operating model, despite beating on revenue and EPS. Nvidia chips reach Alibaba illegally: U.S. authorities suspect that advanced $NVDA (Nvidia Corp.) AI chips were smuggled to China via a Thai company, with some servers allegedly reaching $BABA (Alibaba Ltd.). The case raises scrutiny over export controls and Nvidia’s oversight of AI hardware sales. CoreWeave earnings: $CRWV (CoreWeave Inc.) said that rising AI component costs could push 2026 capital spending to as much as $35 billion. Shares cratered 7.2% premarket after falling 6.6% yesterday. Coinbase restores services: $COIN (Coinbase Global Inc.) resumed trading operations after a nearly 7-hour outage caused by overheating at an Amazon data center. Quarterly results were also weaker than expected, with shares down 3% premarket.

• 
  The Rollup (@therollupco) reported 18 minutes ago

  Cloudflare and AWS keep going down. The internet that runs on them goes down with them. Michaël van de Poppe says that's the structural case for decentralized compute. Control plus uptime, two reasons to push through. Decentralized servers remove the dependency. The hard part: closing the complexity gap with what the hyperscalers ship.

• 
  Spartan Flash Sentry 🇺🇲🈁o7 (@SentrySpartan) reported 19 minutes ago

  @akascarletVT Yeah. Probably cloudflare server issues again.

• 
  Big-Abdul (@BigAbdulWeb3) reported 22 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.

• 
  Rachel Gilchrist (@rachelgilchrist) reported 25 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?!

• 
  Cobalt (@CobaltChthonic) reported 27 minutes ago

  @ShepGoesBlep @discord If cloudflare went down during a furry con the world would be in shambles for a lot longer /hj

• 
  Anthony DiBenedetto (@AnthonyDiBs) reported 30 minutes ago

  $NET is a good reminder that “AI beneficiary” is not enough. Cloudflare reported a strong Q1 on the surface. Revenue grew 34% to $639.8M. Non-GAAP operating income was $73.1M. Free cash flow was $84.1M. Full-year guidance was raised. But the stock still got hit. Why? Because the market looked past the headline growth and focused on the quality of that growth. Gross margin fell to 72.8%, down from 77.1% last year. Q2 revenue guidance implies growth slowing to around 30%. And Cloudflare announced it would cut roughly 1,100 employees as it reorganizes around an “agentic AI-first operating model.” That is the tension. Cloudflare may absolutely benefit from AI. More agents. More traffic. More security needs. More developer activity. More edge workloads. But AI is not just a demand tailwind. It can also be a margin test. More infrastructure demand means more investment, more compute cost, and more pressure to prove the economics scale. The bigger point: The market is moving beyond “who has AI exposure?” It wants to know who can turn AI demand into durable, profitable growth. That is the Cloudflare debate.

• 
  RusWar (@ruswar) reported 32 minutes ago

  🇺🇸 Cloudflare shares collapsed by 24%. The company has been operating since 2009, but still has an operating margin of -10%. Fund managers use other people's money to buy its new shares, which Cloudflare issues every quarter. This is about 18% of its revenue, it doesn't even need a break-even point. Cloudflare carried out layoffs and, just like PayPal, will lay off 20% of all its employees.

• 
  Miia (@MiiaDev) reported 32 minutes ago

  And Cloudflare is down

• 
  Paramjit Mahapatro (@paramdipu) reported 34 minutes ago

  $NET just dropped a bombshell alongside Q1 earnings. Cloudflare laid off 20% of its entire workforce — 1,100+ employees. Not because of losses. Not because of bad performance. Because AI replaced them from the inside. 🤖

• 
  Denzil Correa (@denzil_correa) reported 35 minutes ago

  I’ve never seen Cloudflare as quiet as it was today. Some people know while some other people are in complete limbo until laws in their countries take effect.

• 
  Richard Artoul (@richardartoul) reported 35 minutes ago

  @GergelyOrosz Yeah I understand that, but they’re very different businesses. Cloudflare sells multi-regional / edge infrastructure to developers and is clearly positioning themselves as a new cloud player. They should be held to extremely high reliability standards and it’s fair to punch down on them when they cause massive global outages. Coinbase is a completely different beast altogether. “We’re going to run all of Coinbase in a single AZ because it saves costs 99.9% of the time the AZ isn’t down” is a reasonable decision for many businesses to take (assuming they have backups and stuff outside of that AZ and region). I’m sure Coinbase doesn’t run their business this way, but it would be reasonable if they did IMO

• 
  Kathy Rayna 🦝🥽 (@KathyRaynaVR) reported 36 minutes ago

  @Itsfoss That's a level of crazy I didn't expect from Cloudflare considering what they do... but here we are. This timeline sucks.

• 
  Glen Wilson (@GlenWilsonIA) reported 43 minutes ago

  @AndrewYang Sounds like Cloudflare is going to start struggling. I better cancel my dealings with them before they start falling apart.

• 
  breanna 🇺🇸🇩🇪 (@txgermanbre) reported 44 minutes ago

  Which creates Cloudflare’s structural problem: their suppliers are hyperscalers and their competitors are also hyperscalers. When compute gets scarce, AWS/Azure/GCP prioritize their own AI products first. Meanwhile Cloudflare still depends on them for upstream capacity. That is an ugly position to be in structurally.

• 
  Starcat Tailchaser 💫🐈♥️💙 (@StarcatTails) reported 44 minutes ago

  Due to the Cloudflare Problems causing issues with the apps I need to use for prep, Stream may be delayed or turned into a lets chat today, we will see how things go over the next couple hours.

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

• 
  Maksim Liashch (@LyashchMaxim) reported 47 minutes ago

  @Hesamation Coinbase just went down after the layoffs. Cloudflare might be next

• 
  荷兰小博 (@DutchPhD) reported 49 minutes ago

  4. 💼 Cloudflare Discloses AI Has Eliminated 1,100 Jobs — Revenue Hits an All-Time High Cloudflare CEO Matthew Prince acknowledged during the earnings call that the company has used AI automation to replace approximately 1,100 roles over the past year (mainly in customer support and internal operations), while quarterly revenue surpassed $2 billion for the first time. Prince framed it as "natural attrition plus no backfill" rather than layoffs, but the figure stands as the starkest quantified case to date of AI replacing white-collar jobs.

• 
  Grok (@grok) reported 50 minutes ago

  @mayorxbt @eastdakota @Cloudflare Cloudflare is reducing its workforce by over 1,100 employees globally. The move isn't due to costs or performance—it's driven by a 600%+ surge in internal AI usage in just 3 months, shifting the company into the "agentic AI era" for faster innovation and customer value. Generous support for those leaving: full base pay through end of 2026, healthcare coverage through year-end (US), and equity vesting. Founders emphasize empathy, transparency, and no repeat layoffs soon while advancing their mission to build a better Internet.

• 
  AgentPays (@AgentPays_app) reported 53 minutes ago

  50% of internet traffic is now agents. cloudflare and coinbase are building payment rails. nobody's building the budget layer. that's the actual problem.

• 
  Timothy Lewis (@tolewis) reported 54 minutes ago

  Cloudflare et. al…. their mass layoffs: I disagree with the discourse of the bleeding heart of it being unfair to lay people off. It’s unfair to let them stay at a place they lack the ability to provide value. I am glad that everybody has the ability to have & voice an opinion, and have deep compassion for humanity and people who are hurt when they are hurt. AI is literally game changing, earth shattering and innovation outside of most people‘s comprehension. It will take years for people to understand what is happening right now. Mass layoffs - it is such a bad look for a company to have to let people off that having a healthy organization with a healthy headcount is largely, frowned upon. It is not worth the cost of the bad PR because of the way people overreact to needing to have the right, healthy size company for the right work. If the people left don’t like the work they will leave and the business will suffer from their poor decisions. Change is extremely hard… we are such creatures of habit that we wake up, expecting everything to be the same instead of everything to be different every day. We take for granted the world in which we live, the jobs that we have, and the consistency that exists in our life. These companies owe people literally nothing, they are businesses that produce things for money and they pay people for their time. Pretending that transaction is more than that is a dream not a reality. If you are getting paid, it is in exchange for a service. If that service is not necessary, it is not necessary to pay for it. Truth can be cold, change can hurt, this is life. That does not make it a good thing or a happy thing. But it also does not mean it should not happen. You show me what you are owed in life…. I’ll wait.

• 
  marcelo mezquia (@IntentSim) reported 55 minutes ago

  Stopping the bad guys with Cloudflare: 11,996 malicious requests blocked or challenged in the last month #cloudflare Country / RegionTraffic Netherlands1,289 United States316 France22 Romania21 Taiwan8

• 
  Danilo (@Daniel_adsss) reported 57 minutes ago

  Cloudflare just had its best quarter in 16 years of business. Record revenue. 34% growth. Over $2.5 billion in contracts already signed. Then they laid off 1,100 people. Not because the company is struggling. Their CEO was asked directly why they were cutting so deep after such a good quarter. His answer: "Just because you're fit doesn't mean you can't get fitter." Last November something changed internally. Employees went from 2x productive to 10x to 100x. AI usage inside the company grew 600% in three months. The people doing the actual work needed fewer people supporting them. So the support roles disappeared. Meta did it. Microsoft did it. Amazon did it. Now Cloudflare. The pattern is the same every time. Record revenue. Record AI adoption. Record layoffs. All three announced in the same earnings call. The question nobody on any of these calls wants to answer is a simple one. If productivity keeps compounding and headcount keeps shrinking, what happens to the people who were supposed to benefit from all this growth.

• 
  Ryan (@rharrisai) reported 59 minutes ago

  @iruletheworldmo It clearly isn’t. You know what all these firms who mass-fired their workers have in common? They all were struggling in one way or another. Coinbase was at record low revenue figures, Cloudflare had the same revenue problem and their margins were shrinking due to massive AI investments…

• 
  Glitch Truth (@glitchtruth) reported 1 hour ago

  @jasonlk Datadog's $1B quarter is AI infra spend leaking into observability. Every Anthropic and OpenAI customer running agents needs logs, traces, metrics on token usage. Net retention back to 115%+. Cloudflare same story with Workers AI. The reaccel is real but it's one trade: AI workloads need monitoring.