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	2 days ago
Augsburg	Domains	3 days ago
Montataire	Cloud Services	8 days ago
Greater Noida	Cloud Services	9 days ago
Colima	Hosting	11 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:

• 
  B (@brandonjkingg) reported 2 minutes ago

  @hieuSSR Same issue I had with lovable, switched to cloudflare and now working.

• 
  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 and 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.

• 
  Tawanda Michael Mahere (@tawandamahere) reported 7 minutes ago

  Expect dozens of agents per person. That means the internet may go from ~6B humans to tens of billions of autonomous economic actors. Cloudflare already blocks 2.5B malicious bots daily. But in the future, large parts of internet traffic will come from legitimate agents. Agents online may outnumber humans 1000: 1. Platforms can no longer treat all bots as bad by default. Merchants will need systems that can distinguish verified humans, trusted agents, and malicious automation. This is why the internet increasingly needs proof of human, trusted agent identity, programmable authorization, and verifiable delegation.

• 
  Mr higanste (@higanste) reported 10 minutes ago

  Yo, Cloudflare just announced a 20% layoff—about 1,200 jobs gone. It’s a huge hit for the CDN world and could shake up internet security pricing. Ngl, we might see cheaper plans but also slower support. #Tech #AI

• 
  Ethan (@0xEthanS) reported 11 minutes ago

  idk who shipped the @vercel dashboard UI update, but it may be the worst thing I’ve ever seen. might migrate to @Cloudflare so i don’t have to look at it

• 
  Crossroads (@Dr_Crossroads) 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."

• 
  Deckard 💻 (@deckard_the_dev) reported 13 minutes ago

  My building in public spend so far: Hetzner VPS: $10 Domains: $32 Cloudflare DNS: $0 Cloudflare R2: $0 Resend: $0 X Premium: $36 Total: $78 over a couple of months It has never been cheaper to build

• 
  Tommy D. Rossi (@__morse) reported 14 minutes ago

  feature request for @Cloudflare: I want to create a "deploy to Cloudflare" button for an open source project, I need to be able to prefill an env var/secret using a query param in the deployment url I also need to add a callback url to redirect the user to after the app is deployed I need to customize the env variable per user, I will inject the user_id here, to be able to associate the deployed app with my own database callback url has a similar purpose. to be able to know when the app has been deployed Vercel deploy buttons already support this. I would love to add support for Cloudflare too

• 
  Paramjit Mahapatro (@paramdipu) reported 14 minutes ago

  Cloudflare is paying affected employees full base pay through end of 2026 + US healthcare. That's generous. But it's still a pink slip. The severance doesn't change the signal. 💀

• 
  dennismary_ (@dennismary_) reported 14 minutes ago

  @Dominus_Kelvin Do we really? If you actually need sub-20ms latency today, you don't rent a VPS, you push your state to the edge like @Cloudflare. For heavy compute, an local DC will never beat Contabo or Hetzner on price. What we need isn't local servers, it's to pay local currency.

• 
  MIKS (@MIKS_ae) reported 15 minutes ago

  @galileowilson the fake-Cloudflare-verification scam is the latest social-engineering vector, the keystroke instructions to inject malicious code is the actual payload, sharing the warning is good signal

• 
  Peter Cruckshank (@PeteCapeCod) reported 17 minutes ago

  @eastdakota @Cloudflare Sorry, and that sucks. But if you were going for classy and respectful, you nailed it. I'm sure peeps appreciate it.

• 
  Scott (@scottstts) reported 19 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

• 
  Slim Jimmy (@slimjimmy) reported 23 minutes ago

  @GergelyOrosz all of this AI-washing will catch up with them. the question WILL get asked: where are the goods you promised? and there won't be any because it was to disguise poor performance look at coinbase. eyewatering. i would not be surprised if cloudflare is the same story

• 
  Gus (@guscsales) reported 25 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

• 
  Mufaro (@mufaro_dev) reported 26 minutes ago

  @eastdakota @Cloudflare sorry but blaming this on AI is incredibly stupid, doesn't really help the "AI will bring jobs" case at all, rather dismisses it

• 
  @indiehackingguy💻🛜🎧🚀 (@indiehackingguy) reported 27 minutes ago

  People are sh*tting on Cloudflare right now. But here's the thing - Incentives drive Outcomes. You all know that AI has increased Developer Productivity, and every company is trying to save costs, right! It means the job of 10 developers can be done at the cost of 1 now, because of AI Agents. Hence, businesses are incentivized to fire employees because its helping them reduce cost. ––– So, what's the solution to this? Since developer productivity has massively increased, its never been easier to start your own company, a competitor to an existing software company. A software company which is bloated as f right now, and is firing employees because of it. All the companies right now are moving towards becoming lean till they utilize AI to the maximum. Till the time they feel they aren't doing that, layoffs will continue. Hence this is the time to start your own Software Company - use Local AI Models - use Proprietary AI Models doesn't matter. Just Build. Less Resources. More Intent. Less Human Capital. A Lean Profitable Company that Beats a Bloated Corporate. When Revenues will fall, they will start hiring people again. If developers don't want to understand business, then don't complain when you get fired! ––– ps. - I've created Hermi: an app that helps anyone think critically and make better decisions check it out (link in the 1st comment)

• 
  Neel (@NeelMacro) reported 27 minutes ago

  $NET Cloudflare down 17% , $UPWK down 28% in pre market after earning. Cloudflare beat earnings. Revenue up 34%. Then fired 1,100 humans. AI took their jobs. Upwork connects businesses with freelance workers. Revenue grew just 1.4%. Fewer companies are hiring humans now. Both dropped the same night. Both blamed AI. One is the tool replacing workers. The other is the marketplace losing them.

• 
  Xavier Rivera (@XavierRiveraX) reported 27 minutes ago

  Cloudflare cut 1,100 jobs in its first major company-wide layoff. Record revenue the same quarter. CEO Matthew Prince says AI efficiency gains made support roles unnecessary.

• 
  Roberto Blake 🇺🇸🇵🇦 Creative Entrepreneur (@robertoblake) reported 30 minutes ago

  Cloudflare overhired and never needed 5000 people… You can operate a large scale social network with 1B users with less than that… You can operate all of Steam with 1/10 of that. Before AI as a matter of fact. A lot of companies over hired as a market signal of growth, which jumped their share price. They can now fire, jump their share price, claim it’s AI, jump their share price, and increase productivity.., which also… jumps their share price. These workers will likely also be gone because they have a skill that is highly valued if they were not coasting.

• 
  EnesInvestUS (@enes1050392) reported 33 minutes ago

  Cloudflare $NET | Q1 2026 Earnings Review SUMMARY Numbers beat consensus, full-year guidance was raised, 20% of the workforce was cut as part of a restructuring — and the stock closed down 18%. Not a classic guidance reaction; the difficulty of pricing a company transforming into a different company before your eyes. FİNANCİALS Revenue $639.8M, up 34% YoY — beating consensus by $18M. Non-GAAP EPS $0.25 ($0.23 expected). Gross margin slipped from 75.9% to 71.2%; not structural deterioration but a compositional shift — lower-margin Workers products are scaling faster, and network costs were reclassified from marketing to COGS. The real signal is in cash. Free cash flow hit $84M, 13% of revenue (vs. 11% a year ago). $4.16 billion on the balance sheet, near-zero debt. DBNRR 118%; large customers carry 72% of revenue; 42% of the Fortune 500 are paying clients. EARNİNGS CALL Citi’s analyst delivered the call’s pivotal moment: “With a strong quarter on the table, why this restructuring now?” Prince’s framing was sharp — AI is “the biggest tailwind in our company’s history.” The data backed it: internal AI usage rose 600% in three months, 97% of engineers use AI coding tools, and the Workers platform added 1 million new developers in a single quarter (5.5M total). The operational signal came from the CFO: “We’re north of 46% on Rule of 40 today, with line of sight to crossing 50% next year.” A clear declaration of structural leverage. MARKET REACTİON The stock had run from $135 to $256; positioning was crowded. Q2 guidance landed millimeters below expectations ($664-665M vs. $665.3M) — in momentum names, millimeters compound. Add a 1,100-headcount cut, and selling triggered. The telling comparison: when Oracle and Block announced AI-driven cuts, their shares rallied; NET collapsed. The difference sat in the investor base’s prior. Oracle and Block were already priced for weak growth — cuts read as “margin rescue.” NET carried a 30%+ growth premium — the same cut prompted “why was this needed.” The same action prices differently in different contexts. CONCLUSİON This quarter, NET became two companies at once: the premium growth story the numbers validate, and the operational-leverage narrative of a firm rebuilding itself for the agentic AI era. The thesis isn’t broken; the equation changed. The moat didn’t weaken — it deepened. Distributed network, developer base flowing into Workers, enterprise penetration — none of these replicate easily. The next two quarters are decisive. If Rule of 40 crosses 50%, this drop will be remembered as an entry window. If not, the 18% reaction reads as a warning shot. The earnings rewrote the story, not the stock.

• 
  Xiufeng Guo (@gxf) reported 35 minutes ago

  Cloudflare dashboard is not working on Firefox for several weeks, Chrome only website? @Cloudflare @CloudflareHelp

• 
  Eason 🚀1/15 (@MaberFate) reported 37 minutes ago

  @levelsio Hetzner + Cloudflare CDN = basically unlimited bandwidth for $5/mo. Never paid overage once.

• 
  StocksDaily (@StocksDaily) reported 41 minutes ago

  $NET Cloudflare Q1 2026 results: Revenue $639.8M — beat the $621.9M estimate Adjusted EPS $0.25 — beat the $0.23 estimate Q2 guidance: revenue $664–$665M vs $665M estimate — essentially in line. Adjusted EPS $0.27. Full year outlook: revenue $2.81B vs $2.80B estimate, adjusted EPS $1.19–$1.20 vs $1.14 estimate — raised above consensus. Clean beat on Q1, full year EPS guidance above expectations. Cloudflare keeps compounding. Network security and AI connectivity are both tailwinds for this name in 2026. Not financial advice.

• 
  Aayush Mittal ⚡ (@aayushmittal13) reported 42 minutes ago

  @eastdakota @Cloudflare Severance package through the end of 2026 proves that it’s not a cash crunch issue rather a long term reorganisation exercise

• 
  casslin (@thulynnn) reported 44 minutes ago

  Audio quality of @Cloudflare earning calls is terrible wonder why they pick such platform lol

• 
  DarkRessurect (@DRessurect) reported 52 minutes ago

  @Saviisenpaii Cloudflare problems it seems

• 
  👁 (@musketeers4elon) reported 54 minutes ago

  @REALCalifornian @CargileForCA35 I can't see what is says, because CLOUDFLARE won't let me in when it comes to Fraudlein Hilton, whereas I haven't had problems getting through with other's links.

• 
  mohbi (@mohbii) reported 54 minutes ago

  @CNBC Cloudflare down 18% cutting 1100 while Datadog soars 31% IREN jumps 13% and CoreWeave doubles is AI creating winners and losers at the exact same speed. the infrastructure play wins. the middleman play dies. same technology opposite outcomes. the AI economy is already sorting itself

• 
  FossilSouthie (@SouthieFromSTW1) reported 58 minutes ago

  @Kamoro2611 Nvm cloudflare is dying so this won't fix much rlly😭