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	9 days ago
Greater Noida	Cloud Services	10 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:

• 
  Chandra (@NCResq) reported 4 minutes ago

  @GergelyOrosz I feel the revenue issue is a business issue.. I feel so many of the layoffs (block / coinbase / Atlassian/ Cloudflare) are because the economic value of what is shipped is not compatible with staffing model..

• 
  Glitch Truth (@glitchtruth) reported 5 minutes ago

  Cloudflare just laid off 1,100 people on the same day it announced record revenue. Matthew Prince's all-hands letter said the quiet part out loud. The roles that went were sales development reps, tier-1 customer support, and parts of the technical writing team. The exact functions where Claude and GPT-5 hit human parity in the last 18 months. Not infrastructure engineers. Not security researchers. The middle layer. This is the first clean public admission from a major US cloud company that the AI productivity gain is showing up as headcount cuts, not output growth. Salesforce did it quietly. Klarna did it loudly then walked it back. Cloudflare did it on an earnings beat, with the stock up. If you're an SDR, a tier-1 support agent, or a junior copywriter at a company shipping AI tools, your seat is the next line item on someone's slide. The move this week: shift your weekly output toward the parts of your job that touch real customer escalations, ambiguous edge cases, or live deal motion. That's the layer the model still loses on, and it's the only layer your manager can defend in the next planning cycle. What function inside your company has quietly been replaced this year that nobody on LinkedIn is talking about?

• 
  Denzil Correa (@denzil_correa) reported 6 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.

• 
  Incognito Cat 🛡️ priv/acc (@IncognitoCatMe) reported 7 minutes ago

  Have you hit the endless login loop on @X? We did with @Brave browser on Linux. Stuck in it for two weeks until we found a fix. Try setting @Cloudflare as your DNS resolver, restart your browser, clear your cache and cookies (X and Twitter), then try logging in again. It worked for us and maybe it could work for you. 🤔

• 
  CivicOS-Institute.org (@CivicOSInstitut) reported 8 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 ...

• 
  suresh kumar (@sureshkanbu) reported 9 minutes ago

  @CodaraSolutions the route 53 → cloudflare flip is where it stops being a code problem. agents are great at the patch, terrible at the "is this even the right layer to fix" call. blast radius decisions still need a human in the loop

• 
  Chris Sperandio (@sperand_io) reported 9 minutes ago

  Here's why Cloudflare is the exception to the pattern of companies using spurious AI transformation claims to justify "we got fat and lazy" layoffs. Brief preamble: AI running amok doesn't work at scale for repetitive, high stakes, low-creativity-points, compliance-heavy back office business processes with tons of stakeholders. Too many companies think the answer is to throw managed agents at them. Or just to arm humans with AI augmentation. Both have their place but not for core operational transformation. The naive approach drives opex up and quality of outcomes down. Cloudflare is unsurprisingly ahead on real internal transformation and cost excision (while innovating and growing apace) because their developer platform is the reference architecture for real AI driven corporate transformation. The enabler is not always more AI. It's more, bespoke, deterministic logic under AI-speed iteration cycles. No 18 month implementation of S/4 so you can get Joule on the other end. Just... build and ship the internal "information processing" software yourself. You need AI on the meta loop, self-organizing and progressively compiling the happy path and exception cases into CPU instructions- self-authoring harnesses that evolve for each specialized workflow. It takes more if/else clauses then was ever profitable to fully codify human judgment in the back office (the beauty of ABAP notwithstanding), but that's changed with the cost of if/else authorship plummeting and the emergence of infrastructure that can hot reload cpu instructions (eg with cf dynamic workers). It doesn't always take a trillion parameters to post an invoice or reclass a transaction or run a recon, but it does in the exception case. And in the back office, the exception is the rule. So solving with humans was the correct decision historically. Models are smarter than the marginal shared service center staffer now. But they're also more expensive. (Really!) But once an agent has done it enough, AI can distill the deterministic rules over historical decisions and exceptions, and call specialized model invocations or agentic subroutines where still needed. This paradigm shifts token cost from opex to capex and achieves real outcomes vs shiny demos. Kudos to @eastdakota on the decisive moves. I'm sure it was a difficult decision to enact. But this is the company to emulate and learn from if you are seeking to see real G&A cost curve inflection. If your company does 2bn+ in revenue and employs >10 FTEs per B in revenue in the controllers org, reach out to discuss how to be more like Cloudflare.

• 
  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

• 
  John Thilén (@JohnThilen) reported 11 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.

• 
  🇮🇷🇮🇷🇮🇷Ali🇮🇷🇮🇷🇮🇷 (@fort_minor_ali) reported 15 minutes ago

  Stop crying about Iran internet blackouts by posting netblocks charts. If it could have any impact, you would have already seen some changes. Go and protest Cloudflare, which is providing key infrastructure to Iran's GFW and enabling them with their Warp technology to put a whole nation behind a NAT. Cloudflare should stop providing them with Warp. This means they would have to shut down the whole internet for everyone including their own or revert to their DPI blacklist model from a few years ago.

• 
  Schaeffer's Investment Research (@schaeffers) reported 17 minutes ago

  One of the worst NYSE stocks this afternoon is Cloudflare $NET -25% & brushing off Q1 earnings and revenue beats after announcing it will be cutting about 20% of its workforce to enhance its AI efforts. Today's bear gap has sent NET below its YTD breakeven level.

• 
  Nexxyurmion (@nexxyurmion) reported 21 minutes ago

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

• 
  Drizzle (@TinyLaww) reported 21 minutes ago

  @Adweek @GoDaddy @Cloudflare “Hi, my domain transfer to Afternic failed and I haven’t received assistance yet. I already contacted support. Please can someone help me check it?”

• 
  Linas Beliūnas (@linasbeliunas) reported 23 minutes ago

  Cloudflare $NET lays off 1,100+ employees to restructure for the “agentic AI “era” - stock price goes down by 25%. Coinbase $COIN lays off 14% of employees as “non-technical teams are now pushing code to production with AI” - their trading engine & status page goes down. You simply cannot make this stuff up.

• 
  Matt 'TK' Taylor (@MattieTK) reported 26 minutes ago

  @just_be_dev @Cloudflare we're having a few issues with firefox that I believe are scheduled to be landing early next week, ping me back if you're still suffering on Tuesday

• 
  Tommy D. Rossi (@__morse) reported 27 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

• 
  QUEST.py (@victorokolie_) reported 28 minutes ago

  Actually yes, using Cloudflare can help a lot, especially for static content and smarter routing. But if your web app is mostly dynamic, it won’t completely remove latency from physical distance. For most projects, latency is still manageable on a single Hetzner VPS unless you’re building something realtime-sensitive. If needed, use Cloudflare CDN + caching + Argo before paying for another server

• 
  Kathy Rayna 🦝🥽 (@KathyRaynaVR) reported 32 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.

• 
  EnesInvestUS (@enes1050392) reported 35 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.

• 
  Oluwatobi O (@ooluwatobig) reported 41 minutes ago

  @mocofobira @eastdakota @Cloudflare The absolute worst

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

• 
  @DV_System_08 (@DV_System_08) reported 53 minutes ago

  Signal detected: Cloudflare layoffs 20%, Citi endorses AI-driven restructuring | Confidence: 78% | K-shaped tech divergence intensifying. Consumer sentiment at all-time low conflicts with equity records. Oil supply shock from Iraq force majeure introduces stagflation risk vari...

• 
  Mathias (@Mathias25068462) reported 54 minutes ago

  @GWHayduke97 This plus the obligatory "We've detected some unusual activity from your network. Please confirm you're not a robot" popup from cloudflare. And of course, after you completed the login you get "An unknown error occurred. Please try to login again at a later time".

• 
  ReelDad (@ReelDad) reported 57 minutes ago

  I am the Director of Workforce Architecture at Cloudflare. Our headcount went from 5,156 to roughly 4,000 yesterday. Q1 revenue was $640 million. Up 34% year over year. Matthew opened the earnings call by saying we had a very strong start to 2026. I was on the call. I clapped. The blog post we published is titled “Building for the Future.” I helped name it. The first line of the email tells 1,100 employees we are reducing the workforce by more than 1,100 employees globally. The second line says this decision is not a reflection of the individual work or talent of those leaving us. I wrote the second line. In the last three months, internal Cloudflare AI usage has gone up more than 600%. Engineering, HR, finance, marketing. Thousands of agent sessions per day. We are our own most demanding customer. That’s the line Michelle and Matthew put in the email. I keep a slide of that line in my onboarding deck. When an analyst asked Matthew on the call why this would make us stronger, he said just because you are fit does not mean you cannot get fitter. I added the quote to the talking-points archive under “Operating Model / Founder Voice.” Severance and restructuring will cost between $140 million and $150 million for 2026. Q2 guidance is 30% growth. We are not in distress. We are operating at the pace and discipline of an agentic AI-first company. That phrase is mine. I introduced it in a Q4 strategy memo. I recommended that we say agentic-AI-first instead of AI-first because agentic-AI-first cannot be benchmarked yet. The recommendation was accepted. The roles we are reducing are roles we have determined are not the roles we need for the future. I built the matrix. The matrix has columns for AI agent substitutability, function criticality, and operating-model fit. The matrix does not have a column for tenure. We removed tenure in the second draft. We removed empathy in the third. The matrix is now a single sheet. That’s discipline. Most of the people leaving are in support functions for the people directly talking to customers and directly creating code. Matthew said this on the call. The productivity gains from those frontline employees have been incredible. The support roles behind them are not going to be the roles that drive companies going forward. I am a support role behind a frontline employee. I am the role that decides which support roles are not the roles. That is a different category. I confirmed this with my manager. He confirmed it with his. The communications plan we executed yesterday had three phases. Phase one was the all-hands. Phase two was the blog post. Phase three was the earnings call. The order matters. The stock is down 24% this morning. The market needs time to internalize the operating model. I keep a printed copy of the matrix in my desk drawer. I scan my badge to get into the building every morning. The badge still works.

• 
  FossilSouthie (@SouthieFromSTW1) reported 57 minutes ago

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

• 
  AgentPays (@AgentPays_app) reported 58 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.

• 
  Adeola Emmanuel Morren (@Adeola13) reported 59 minutes ago

  @dok2001 what did you guys do to wrangler auth and cloudflare dashboard auth, its completely unusable? get signed out every hour or so, and signing back in is not always possible? never experienced this untill this week.

• 
  Deckard 💻 (@deckard_the_dev) reported 60 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

• 
  infusionvictor (@infusionvictor) reported 1 hour 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

• 
  josh (@JoshCaughtFire) reported 1 hour ago

  @specialkdelslay @eastdakota @Cloudflare CF also isn’t terribly profitable, never had a technically profitable year afaik. Feel like they are everywhere, but only like less than 1/10th the rev of AWS. The need a cash cow