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 (41%)
• Cloud Services (33%)
• Hosting (18%)
• E-mail (4%)
• Web Tools (4%)

Live Outage Map

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

City	Problem Type	Report Time
Greater Noida	E-mail	4 hours ago
Paris	Domains	1 day ago
Crisfield	Domains	2 days ago
Noida	Hosting	6 days ago
Augsburg	Domains	7 days ago
Montataire	Cloud Services	11 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:

• 
  Dystopic Winter (@dystopicwinter) reported 5 minutes ago

  Cloudflare just laid off 1,100+ employees. Their reason? Internal AI usage jumped 600% in 3 months. They said it themselves — they don't just sell AI, they ARE their own most demanding customer. Here's what nobody wants to admit: this is the playbook. Every tech company watching Cloudflare is taking notes. Not because they want to, but because the math forces them to. When your own AI agents can do what 1,100 humans did, you don't keep the humans and feel good about it. You cut. And the ones who don't cut fast enough get eaten by the ones who do. This isn't a Cloudflare problem. It's a preview. The question isn't if your employer replaces you with AI. It's whether you're the one building the AI or the one being replaced by it. Build leverage or become leverage.

• 
  rosecoco (@_rosecoco) reported 6 minutes ago

  @gocodejack Cool Name. Use Cloudflare for DNS for the SSL issue.

• 
  Kevin (@kcosr) reported 6 minutes ago

  @theodorvaryag @notnullptr Cloudflare WARP works well for me. I get a tunnel to my home network and can even resolve local DNS on my phone.

• 
  AliceMia (@Alice_MiaX) reported 8 minutes ago

  $COIN just cut 700 employees. 14% of the company. Gone. The CEO says AI layoffs are coming to "every company." Not someday. Now. Coinbase is replacing managers with "player-coaches" and building one-person AI teams that do the work of entire departments. They're calling them "AI-native pods." One person directing AI agents that handle engineering, design, and product management. Entire teams replaced by one person and a prompt. $50-60 million in severance charges hitting Q2. Stock went up on the news. Revenue is fine. They just don't need the people anymore. This isn't a Coinbase problem. Cloudflare cut 1,100 the same week. PayPal cut 4,500. All citing AI. All posting record revenue. The pattern is getting loud. 👀

• 
  Purvi Shah (@shahpurvi1607) reported 8 minutes ago

  Cloudflare is slashing their 20%of staff and planning to invest in AI and agentic Workflows? Do we really need to invest in AI at the cost of people's salary ? This will automatically slow the economy and turn the markets down

• 
  GΛB🪐 (@CosmoGabs) reported 9 minutes ago

  Cloudflare $5/mo is the best gateway drug in the world. By the time your bill goes higher, you are officially in “nice problem to have” territory. And at that point you’ve realized they deserve your money. First 3,000 outbound emails are free, too. Every month.

• 
  38twelveDaily (@38twelveDaily) reported 9 minutes ago

  Cloudflare just laid off 1,100 people—20% of its workforce—while posting record $639.8M quarterly revenue. CEO Matthew Prince says AI made the support roles obsolete, not financial pressure.

• 
  Muhammet A. 👉🏻 Mobile Dev (@indiesoftwaredv) reported 10 minutes ago

  @coderjunior7 @Cloudflare It is a video hosting and delivery service

• 
  Tom Kang (@mobilekang) reported 10 minutes ago

  @MohitOpinion Great post Mohit! Can you explain a bit more on the AI cost problem for Cloudflare?

• 
  dex (@dexterxbt) reported 11 minutes ago

  @shawn_dot_so @levelsio @Cloudflare no you don't, you just need to be a EU citizen. but yeah ccTLD requirements are why Cloudflare doesn't support most of the 2-letter TLDs

• 
  Hermann (@dhlotter) reported 11 minutes ago

  Shipped a feature that uses GA4, PostHog, and Cloudflare Insights. Took four separate PRs just to get the Content Security Policy right because every tool loads scripts from a different host. CSP doesn't punish bad code. It punishes third parties. #buildinpublic #WebDev

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

  Today isn't catgirls stream day HOWEVER! due to cloudflare and discord issues on last friday would you like me to stream Pragmata today? or should I do it on the normal day - Friday and catgirl gets to rest? Vote quick only one hour to decide

• 
  Sina Meraji (@sinasanm) reported 18 minutes ago

  kimi k2.6 has a 256k context window which is well below the 1M context window of opus 4.7 and other great models. therefore since the beginning i've intentionally built different mechanisms into kimiflare (claude code clone with kimi k2.6 + cloudflare) to make sure when i use it i feel as productive as when i use claude code, or more productive. i've built good products and bad products in the past, for myself and others, so my overall principle when i build anything now is that i dont put up with BS, especially when it comes to using products, and that im equally capable of building BS products as i am of building great products. therefore in the context of kimiflare, my primary guiding question has been "i know it's fun, but is it also great or is it bs?". in this case, turns out i actually really really like kimiflare and have been using it exclusively as my terminal ai coding tool. like when i started building it, the very first night i made the first 2-3 commits with claude code and at that point i wasnt thinking too much about whether or not this is gonna become useful. i just thought "oh a frontier open source model dropped and it's on cloudflare and i have some cf credits that expire in 2 weeks, let's build a claude code clone" and of course by default i assumed it was gonna suck. but as soon as i switched to the kimiflare MVP to continue building it with itself (from a very early version), i had an instant aha moment which was "oh **** this actually works and it's fast". of course i inherit a big part of that aha moment from @Kimi_Moonshot and @Cloudflare so i dont wanna be delusional. when i start with an impressive model and host, naturally my starting point for quality is somewhat elevated. but that doesn't automatically give me a no-bs product that i, as a 31 year old no bs adult in 2026 would personally use in private when nobody's watching, on a daily basis. that's the part that won't happen automatically, im supposed to make that happen. AI and infra companies are cooking but the burden is still on the builders. to make the question of quality objective, i ask myself "does kimiflare just work or does it have a non-zero chance of being objectively great?" and "how far can i push it before it either cracks or becomes a memory on my github." as of today, several people are using the cloud version and have exhausted their 5M free tokens and have DMed me for more, and some of those are way past 20M tokens in their day 1. maybe their state of mind is "im tolerating this scrappy silly product that shouldn't exist but i want more tokens because it works" or it's "oh wow it's actually pretty good". i dont know, im just gonna look at the usage stats. monitor the situation. so coming back to the 2 things at the start: the capped context window, and the question of whether this is actually quality or just bs. i've been experimenting with and introspecting on how to build an architecture where context window is capped, at least temporarily until these models catch up, while making sure as a user you don't feel handicapped. you should feel equally or more powerful. people want to import all their agent skills, they want long sessions with extensive plans and full project context loaded in, they want all the things that high-context window models give you. and i've needed to redesign and rethink many of these to make that work under the constraint. for example i've built a custom triage architecture that's pretty simple but im quite proud of. it does a decent job of deterministically scoring task complexity and identifying user intent and routing to a suitable agent behavior accordingly (fast and short with limited skills equipped vs deeper engagement and tools and skills etc.) there are a bunch of bets i've been taking. some of them are working really well, and i have a bunch more. gonna write about that sometime

• 
  Moe⚡️ (@moeghashim) reported 19 minutes ago

  @levelsio Yeah yeah.. My question wasn't clear. I meant anything from Cloudflare other than email service?

• 
  Dan Melnick (@DanPMelnick) reported 19 minutes ago

  Cloudflare just eliminated 20% of its staff while citing massive AI productivity gains. 1,100 employees. Gone in a single announcement. What organizational compression means for you: your engineering function could be next. Coinbase cut 14% of its staff, noting engineers now ship in days instead of weeks. Block reduced its workforce while leaning into AI efficiencies. All restructuring simultaneously. The industry calls it an AI-first transformation. This is not a headline about tech layoffs. It is a headline about workforce architecture. The function is being rebuilt around new pillars: system design, AI code review, and high-level problem solving. The goal is to organize around the capabilities that will matter most next. That sentence deserves a second read. Because it does not describe the roles being eliminated. It describes the roles replacing them. The new structure does not replicate the old one with fewer people. It is built around fundamentally different assumptions about what developers can do when AI handles the syntax and repetitive layer. This is the pattern I have been tracking across software development for months. Meta moved to leaner teams. Amazon restructured around AI operations. Now the industry is not just compressing headcount. It is redesigning the logic of how a build operates. I watch a version of this happen firsthand every day at Zing. We use our Six-Step Software Methodology to cut development time by 40%. The part that never makes the headlines: the developers who stay do not keep their old jobs with AI bolted on. They get entirely new jobs. Writing code becomes reviewing code. The skillset changes. The bottleneck changes. The definition of what "good" looks like changes. AI handles the volume, while humans handle the 20% that requires strategy, architecture, and judgment. That is the difference between task automation and structural redesign. Task automation makes people faster. Structural redesign removes the need for the old architecture entirely. Most dev shops are still doing the first. The smart ones are doing the second. Here is what concerns me. The gap between what AI enables and what most organizations have actually restructured around continues to widen. AI-forward teams are on one side of that gap. Almost everyone else is on the other. And the distance between the two groups is growing every quarter. Your CTO is watching this. Your board should be too. The question worth raising in your next leadership meeting is not "how do we make our developers code faster with AI." It is: if we rebuilt this function from scratch around AI-era capabilities, what would it look like? Not which roles become faster. Which roles shift entirely to system design. And what replaces the junior work. Most organizations are not asking that question yet. The winners just did.

• 
  Sanidhya Shishodia (@iisanidhya) reported 20 minutes ago

  Cloudflare cut 1,100 jobs. 20% of its workforce. reason given: internal AI usage went up 600% in three months. the company building the infrastructure for the AI revolution is being restructured by the AI revolution. I build agents on top of Cloudflare's edge network. the platform I depend on is being disrupted by the category I'm building in. the irony runs all the way down. #AI #tech

• 
  Bowie (@bowieoverride) reported 21 minutes ago

  Did a call with a cloudflare sales rep for enterprise, he said “our worst competition is ourselves”

• 
  Shimazu.S (@ShimazuSystems) reported 22 minutes ago

  The reality is that people will continue using it, because (just like cloudflare) it brings down costs. The more individual/unique apps & sites pop up, the less likely it is that anyone will pay for them, so why would you not cut costs where possible? I don't use either, but I do see why people do & will continue to + I cannot see any kind of human verification *not* being invasive - now the pandoras box is open, it is inevitable people request walled gardens free from AI. At this point what do you do?

• 
  Phil (@0xPhilH) reported 22 minutes ago

  @milanm_ @levelsio @Cloudflare To add here, since CFs offices are in France, they overcomply with every bs EU request, even if you host a service that is US only. They won't do that for the content part, so namecheap registar + CF dns + CF CDN is actually best of both worlds combo.

• 
  Bunty (@HeyItsBunty) reported 29 minutes ago

  @levelsio @Cloudflare everyone chases the cheapest tool until their login emails vanish into spam. Cloudflare wins on price, loses on battle-tested reputation.

• 
  Somi AI (@somi_ai) reported 33 minutes ago

  @ayushagarwal @dodopayments @Cloudflare what's the routing signal, user-agent or accept header? UA spoofs trivially but accept: text/markdown would be the cleaner contract if agents start setting it

• 
  Rombaro Rory (@psimatrix) reported 37 minutes ago

  @bendee983 Cloudflare already converts all your pages to Markdown on AI agent requests, with one toggle. If you never implemented Structured Data Objects on your site, this is a mediocre solution, if you did, this gives AI two alternative paths to understand your content. Good engineers already did this and aren’t behind, they are two steps ahead of this conversation.

• 
  🏴‍☠️CyberTechWolf🏴‍☠️ (@CyberTechWolff) reported 38 minutes ago

  @vxunderground Cloudflare can go **** themselves they don't control the damn Internet abolish ******* Cloudlare!

• 
  Disengage9090 (@Disengage9090) reported 39 minutes ago

  @HiveHelper why does the Hive Hub make constant DNS over HTTPs requests to various Public DNS Resolvers? Every 5 minutes the hub is trying to connect to either Cloudflare DNS, Quad9 DNS or Google DNS over port 443. I block all public DNS resolvers on my home network, so why…?

• 
  Marcus V (@EudoraFenty) reported 41 minutes ago

  Tech stocks just had the most extreme day of divergence! Cloudflare crashed 24% while Innodata surged 86%! That's a 110% spread! Cloudflare plummeted 24% to $196.13, making it the biggest loser on the board. HubSpot dropped 19%, Mettler-Toledo fell 15%. On the flip side, Innodata exploded 86% and Akamai jumped 27% on strong earnings. Wall Street is debating whether AI is replacing jobs or transforming them. Let me break it down: why are companies in the same sector moving 110% apart in a single day? The core reason: Wall Street has absolutely no consensus on AI's real impact on employment and tech company revenues. Previously, anything with "AI" in the name went up. Now investors are doing actual math. If AI truly replaces lots of jobs, tech companies that sell human-labor services to enterprises will see their revenue shrink. But companies actually earning real money from AI? Those get bid up aggressively. Analogy time: a giant fresh food warehouse is about to open in your neighborhood. The small grocery delivery guys? Everyone assumes they're done for, so their business asking price drops 30%. But the suppliers and equipment providers for the new warehouse? People are fighting to invest, bidding up their valuations 86%. Two practical takeaways: 1. AI divergence = tech stock daily swings will be at least 2x larger than before = if you hold broad tech funds, single-day losses of 20% are now 3x more likely. Don't chase momentum blindly. 2. Avoid companies that only have AI buzzwords but no actual AI revenue. Focus on companies with demonstrable AI-driven profits. Stay away from tech stocks whose core revenue depends on human labor services with no clear AI transition plan. My prediction: Tech stock divergence will intensify over the next 3 months. The cumulative spread between AI winners and AI losers could exceed 120%. Risk: if AI commercialization disappoints, both categories could see 15%+ pullbacks.

• 
  Oversized Moose With Socks (xlmoose.eth) (@undacappn) reported 42 minutes ago

  @levelsio @misterrpink1 @Cloudflare That sucks, please stop

• 
  UntappedAI (@UntappedAIHQ) reported 45 minutes ago

  Layoffs Cloudflare cut 20% of its workforce after internal AI usage jumped 600% in three months. This is the pattern. AI adoption goes up. Headcount goes down. The companies adapting fastest are pulling ahead. Which side of this are you on?

• 
  Iarimas (@Iarimas7) reported 49 minutes ago

  @IdleIrkutsk @gelbooru @Cloudflare Platforms are free to enforce their personal rules however they wish to. 2 problems with this instance: 1. Cloudflare is claiming it's against, "Foreign laws" which Gelbooru from what I understand is stationed in US where the law is not against this material.

• 
  Precious | The App Guy 💙 (@precious_tagy) reported 50 minutes ago

  @akinkunmi 1. kinda tiny to be called one tho :) I do just refer it to as a media service running on cloudflare edge 2. absolutely not ? Why What wrong in hosting your dashboard where you put your user facing api on a vps Putting them inside a container on the same VPS ?

• 
  Iza (@izadoesdev) reported 57 minutes ago

  @niveditjain nobody really has time to deal with AWS's bs at this point, I'd rather pay a premium for resend or cloudflare to deal with it for me all the IAM policies, terrible UX, terrible billing, and complexities, not to mention needing to apply for it not a good experience