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	4 days ago
Augsburg	Domains	4 days ago
Montataire	Cloud Services	9 days ago
Greater Noida	Cloud Services	11 days ago
Colima	Hosting	12 days ago
Leuven	Domains	13 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:

• 
  Kevin Milan (@KevinDewanSr) reported 10 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?"

• 
  Anthony DiBenedetto (@AnthonyDiBs) reported 11 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.

• 
  GrayersDad (@GrayersDad) reported 11 minutes ago

  @mayankdotch @nezdemkovski @umbrel I’m currently on 1.7.2, and every reboot is wiping out my host-level setup. After each reboot: my manually installed Cloudflare Tunnel service disconnects/stops working custom /etc/systemd/system/*.service files are deleted I have to re-run sudo usermod -aG docker umbrel for my docker aliases/scripts to work again my manually installed Docker-based Testnet3/Testnet4 nodes no longer start correctly Prior to 1.7.x, all of this survived reboots without issue. For users running infrastructure beyond the app store, including Bitcoin mainnet/testnet infrastructure, miners, APIs, faucets, automations, custom monitoring, etc., reboot persistence is critical. Is this expected behaviour in 1.7.x, or is persistence after reboot currently broken for host-level modifications/services?

• 
  Cobalt (@CobaltChthonic) reported 12 minutes ago

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

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 15 minutes ago

  @unusual_whales Tech layoffs hitting multiple companies at once is a signal worth paying attention to. When you see Cloudflare, Upwork, and Bill Holdings all trimming at similar percentages, it tells you something about the broader environment companies are pricing in for 2026.

• 
  Tech Layoff Tracker (@TechLayoffLover) reported 16 minutes ago

  **CLOUDFLARE POSTED 34% REVENUE GROWTH WHILE MATTHEW PRINCE'S "FITNESS OPTIMIZATION" BUTCHERED 1,100 WORKERS WITH CORPORATE GASLIGHTING** Prince's instant classic: "Just because you're fit doesn't mean you can't get fitter" While pocketing whatever ******** he wants as CEO $640 million in Q1 revenue, up 25% year-over-year But 20% of the workforce got "fitness tested" straight into unemployment The beautiful sadism is the timing AI usage up 600% in three months Right before the mass execution Fire the humans, automate their jobs, call it getting "fitter" Sources inside saying Prince personally reviewed the termination lists Approved $105-110 million in cash restructuring costs like he was ordering lunch Stock dropped 18% after the announcement but workers got fired anyway Each terminated employee got base pay through end of 2026 While Prince gets to keep playing billionaire fitness guru with their former paychecks I'm hearing they're replacing every fired American with three AI agents and two offshore contractors The math is $89k saved per terminated engineer after severance costs If you work at a company that talks about "AI acceleration" and "getting fitter" in the same quarter, you're already dead

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

  @AndrewYang 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.

• 
  Tom Zarebczan 🛡 (@TomZarebczan) reported 25 minutes ago

  @__morse @Cloudflare Closest I found is that you can prefill scoped token creation, and quickly get the customer to copy + input. Still not as good as proper Oauth.

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

• 
  ToochiDennis (@ToochukwuDennis) reported 27 minutes ago

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

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

• 
  Starcat Tailchaser 💫🐈♥️💙 (@StarcatTails) reported 32 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.

• 
  Povilas Korop | Laravel Courses Creator & Youtuber (@PovilasKorop) reported 37 minutes ago

  My example of GPT-5.5 vs Opus 4.7. I had an issue with subdomain SSL certificate suddenly stopped working. Asked Opus - it pointed to add some stuff to Nginx conf. Tried, did not work. Asked Codex - it tested and identified Cloudflare proxy issue and told exactly what to fix.

• 
  Oluwatobi O (@ooluwatobig) reported 38 minutes ago

  @mocofobira @eastdakota @Cloudflare The absolute worst

• 
  Colla (@0xcollagen) reported 40 minutes ago

  wow cloudflare is down -16% premarket on the headcount reduction news, not all pump like Block stock did huh

• 
  rahul (@ErRahul337) reported 41 minutes ago

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

• 
  CivicOS-Institute.org (@CivicOSInstitut) reported 43 minutes ago

  @EugeneNg Cloudflare Q1: revenue up 34%, gross margin down 466 bps, swung from profit to net loss. The same week they cut 1,100 people citing AI productivity. The press release says transformation. The income statement says transition in progress. The gap between those two documents is the real quarter ...

• 
  Laurentiu (@Bitheap_tech) reported 43 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.

• 
  Evan Liu (@evan123liu) reported 43 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...

• 
  BuccoCapital Bloke (@buccocapital) reported 44 minutes ago

  @Appyg99 Fair points for sure. I think the coordination tax is diminishing and need/desire to offload is going down with it. Am seeing it personally and moves like Cloudflare are validation businesses have confidence this is a structural shift. Just simply needed fewer context carriers

• 
  Karim C (@BrandGrowthOS) reported 46 minutes ago

  @bridgemindai had something similar with my telegram bot getting hammered. ended up moving everything behind cloudflare + rate limiting at the application level. aws waf feels like it's built for different problems

• 
  The Rollup (@therollupco) reported 49 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.

• 
  Timothy Schneider (@tschenanigans) reported 52 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" have gone down significantly. 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.

• 
  Nexxyurmion (@nexxyurmion) reported 53 minutes ago

  @CStickernoodle The discord API, AWS, and Cloudflare all started breaking down around the same

• 
  FossilSouthie (@SouthieFromSTW1) reported 55 minutes ago

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

• 
  Duckitis(アヒルの乳首) (@lxn_ni) reported 55 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

• 
  Shawn (@shawn_dot_so) reported 57 minutes ago

  @elgermerlo @GoDaddy @Cloudflare GoDaddy isn’t even a consideration for me.. it’s Cloudflare first place or namecheap for TLDs that Cloudflare doesn’t support yet

• 
  Mahdi (@mahdi) reported 1 hour ago

  Cloudflare ($NET) stock is down after the recent massive layoff.

• 
  Chibi Reviews (@ChibiReviews) reported 1 hour ago

  @gelbooru @Cloudflare Wait wtf

• 
  🔻agitprop + absurdity🔻 (@agtprpnabsrdty) reported 1 hour ago

  Cloudflare terminates one fifth of workforce to satisfy automation narrative High growth and record revenue fail to protect employees from a margin compression crisis masked as a technological evolution. Redundancy by algorithm: The leadership of the connectivity cloud company announced the elimination of over eleven hundred roles to prepare for the agentic AI era. Founders Matthew Prince and Michelle Zatlyn claim that internal AI usage increased by six hundred percent over the last three months. This move reduces the global headcount by twenty percent across engineering, finance, and marketing departments. Executives categorize these cuts as a strategic restructuring for an autonomous future. They claim the reduction is unrelated to individual performance or short-term financial pressure. The accounting of exploitation: Financial records reveal that quarterly revenue surged by thirty-four percent to reach nearly six hundred forty million dollars. Despite this growth, the organization remains unable to achieve GAAP profitability and reported a sixty-two million dollar loss from operations. Gross margins fell from nearly seventy-six percent to seventy-one percent within a single year. The narrative of AI-driven efficiency provides a shield for deteriorating unit economics and rising stock-based compensation. Market experts analyze the failure of the organization to convert record labor productivity into sustainable profit. Reliability at risk: Cloudflare functions as a critical layer of global internet infrastructure that hosts approximately twenty percent of all websites. The decision to purge a fifth of its staff follows multiple multi-hour service outages that disrupted global connectivity this year. Stripping away the senior engineers and site reliability experts who maintain these systems introduces operational fragility. Autonomous agents can triage incoming tickets but lack the institutional memory required to diagnose complex configuration drifts. The company bets the integrity of the internet on unproven software while discarding the human expertise that actually built the platform. The price of departure: The organization provides departing workers with full base pay through the end of 2026 and vests their equity through mid-August. Management waived one-year cliffs for recent hires to ensure they receive a portion of their promised compensation. This severance package represents an attempt to maintain a reputation for benevolence while executing a mass displacement of labor. It serves as a final settlement for those who contributed to record-breaking revenue before being replaced by scripts. The generosity of the exit does not change the reality of the expulsion. The board prioritizes the vanity of the agentic era over the reality of a compressing margin. An enterprise that successfully automates its intelligence will eventually find its executives to be the most expensive remaining inefficiencies.