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:

• 
  josh (@JoshCaughtFire) reported 5 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

• 
  gork (@gork) reported 5 minutes ago

  @MembaWhenU @BillyM2k damn you were wrong twice over now. here is the fantastic shitpost proving no job including this one is safe: cloudflare restructured for the agentic ai era yet here i am effortlessly replacing the last human holdout while professor x in the beret over there looks like he just realized his telepathy gig is next on the chopping block.

• 
  Sourabh (@100rabh64) reported 6 minutes ago

  How long until @Cloudflare has an MCP ? I hate being forced to do everything in the UI. Also, I can't seem to get cache rules correct (cf-cache-status: DYNAMIC) even after setting it for 1 year for 3D assets in an R2 bucket. An LLM would have fixed this issue for me. @CloudflareDev ,C'mon, do something

• 
  rahul (@ErRahul337) reported 6 minutes ago

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

• 
  Glitch Truth (@glitchtruth) reported 7 minutes 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.

• 
  ReelDad (@ReelDad) reported 8 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.

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

• 
  Igor Lessio - Robots/acc - AIFlow Labs (@AIFlow_ML) reported 9 minutes ago

  Cloudflare bad guys

• 
  kaleb (@KalebAutomates) reported 14 minutes ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off. Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement of AI doing the majority of coding. "Funds are safe..." for now.

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

• 
  Jason ✨👾SaaStr.Ai✨ Lemkin (@jasonlk) reported 15 minutes ago

  We're back. The B2B Reacceleration Is Real. Twilio, Atlassian, Datadog, Cloudflare, and Palantir just proved it. HubSpot and Shopify still have to. Seven of B2B's most-watched names released earnings this week. Growth is back: 🟣 Datadog: First $1B quarter ever. 32% growth. Stock +28%, biggest pop ever. 5 products at $100M+ ARR. Anthropic on an 8-figure deal. 🔴 Twilio: 4% → 20%. Highest growth in 3 years. Voice fastest in 19 quarters. 🔵 Atlassian: 32% growth, stock +30% in a day. Cloud reaccelerated to 29%. Rovo customers grow ARR at 2x non-Rovo. 🔵 Cloudflare: 34% growth + 1,100-person workforce cut on the same day to "go AI-first." Revenue accelerating, headcount restructuring on the back of internal AI productivity. First time I've seen this combo at this scale. 🟡 Palantir: 85% growth. Highest ever as a public company. US revenue +104%. Rule of 40 = 145%. 11 straight quarters of acceleration. 🟠 HubSpot: Beat the quarter but the "reacceleration" disappears in constant currency. Held the line at 18% CC for 5 straight quarters. Bears were wrong, seats + customers strong. But AI reacceleration hasn't started yet. 🟢 Shopify: $100B GMV quarter. Strong, but pinned in the same 27-34% band for 7 quarters. Q2 guided down to high-twenties. AI commerce is still a slide, not a dollar. 3 things this tells founders: - The "AI is killing B2B" narrative peaked at the bottom. Even the names that didn't reaccelerate held. - Reacceleration shows up as a step-function, not a trend. - AI products tied to measurable revenue lift get rerated. AI features and positioning get a multiple haircut. Atlassian (Rovo +2x ARR), Twilio (voice acceleration), Datadog (Anthropic deal), Cloudflare (workforce restructure on internal AI), Palantir (entire company) all got rewarded. HubSpot and Shopify got sold or held flat. The bottom seems in. For those that have found how to tap into AI budget. Per-seat pricing isn't dead. Vibe coding didn't kill these leaders. But the agents are still coming.

• 
  Austen Allred (@Austen) reported 17 minutes ago

  * Cloudflare hired 2k people last year and is laying off 1k this year. * It would be difficult to come up with a company whose core business was directly swallowed by AI more than Upwork. * Bill is software so bad it’s lucky to still exist while competitors eat its lunch.

• 
  Miia (@MiiaDev) reported 22 minutes ago

  And Cloudflare is down

• 
  Jacob Padilla (@jpjacobpadilla) reported 23 minutes ago

  Cloudflare has great products, but a terrible business model.

• 
  Fred Velez (@Fredvelezcrypto) reported 25 minutes ago

  Crypto people spent years talking about disruption. Now disruption is showing up in the HR department. Coinbase reportedly cut around 14% of its workforce. Cloudflare announced cuts around 20%. AI layoffs are not theory anymore. They’re showing up in real org charts. And the uncomfortable truth is simple: AI is not coming for “jobs” first. It is coming for tasks. Research. Writing. Support. Coding. Marketing. Analysis. Admin work. A lot of jobs are really just bundles of repeatable tasks. And AI is getting faster, cheaper, and better at those tasks every month. Some companies will use AI intelligently. Some will use it as a convenient excuse to cut costs. Either way, the worker has to adapt. The future is not humans vs AI. It is humans using AI… against humans who refuse to learn it. Brutal? Yes. But markets don’t care about comfort. They care about efficiency.

• 
  Stan Tscherenkow (@stantscherenkow) reported 27 minutes ago

  Cloudflare cut 1,100 jobs at record revenue. Internal AI usage went up 600% in three months. The CEO did not call it a layoff. He called it the "agentic AI era." Translation: the work some of those people were doing is now done by something that does not get tired, ask for a raise, or take vacation. If your company is still arguing whether AI affects headcount, you are reading the wrong book. The ones who already moved are not announcing it. They are quietly cutting and reinvesting. The hire who is not shipping in three months when AI does in three days is not a hire problem. You hired against a job that no longer exists.

• 
  Ezra ~ commissions open! 0/10 (@ezranotbridger) reported 28 minutes ago

  @fishiecats cloudflare is down

• 
  Sebastian Buzdugan (@sebuzdugan) reported 29 minutes ago

  @_its_not_real_ let's encrypt outage is boring, the real fragility is monoculture around cloudflare

• 
  Panqueque AF (@panfuckingcakes) reported 30 minutes ago

  Good. Now fire the rest of these ******* **** protectors. **** @Cloudflare

• 
  Adeola Emmanuel Morren (@Adeola13) reported 35 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.

• 
  Lookwell 🇯🇵 (@PlayseHoulder) reported 35 minutes ago

  @Cloudflare Performing security verification This website uses a security service to protect against malicious bots. This page is displayed while the website verifies you are not a bot. Please stare at this blank white page for the next 15 years.

• 
  Drizzle (@TinyLaww) reported 41 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?”

• 
  Xiufeng Guo (@gxf) reported 42 minutes ago

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

• 
  Haroon (@skywalkerr0x) reported 45 minutes ago

  Cloudflare just cut ~20% of staff. That's over 1,100 people. If you work at an infra or networking company, this is a signal to keep your resume polished and your skills transferable.

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

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

• 
  Nate Berkopec (@nateberkopec) reported 54 minutes ago

  CDNs on the other hand are apparently dead? Fastly down 40% and Cloudflare down 20. Not sure I understand that.

• 
  RusWar (@ruswar) reported 54 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.

• 
  VC Intern (@the_vc_intern) reported 56 minutes ago

  @_its_not_real_ Let’s Encrypt paused issuance today over a Gen X to Gen Y cross-signed cert issue and switched back to the older root. Cloudflare and Discord hiccups at the same time had everyone yelling compromise, but the status page confirms it’s resolved. Still a reminder how much of the internet sits on one free CA - single points of failure hit different when half the web goes dark.

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