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 (35%)
• Cloud Services (26%)
• Web Tools (17%)
• Hosting (13%)
• E-mail (9%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Cloud Services	13 days ago
New York City	Hosting	16 days ago
Manchester	Domains	1 month ago
Angers	Cloud Services	2 months ago
London	Domains	2 months ago
Noida	Hosting	2 months 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:

• 
  LayerX (@LayerXlab) reported 6 minutes ago

  You close your laptop, and your coding agent usually dies with it. @ickasdev built a fix: a DGX Spark running as an always-on box for Claude Code, gated behind Cloudflare Access, with one session that follows him from the box to his laptop to his phone, without handoff. He wrote up the full setup: the control plane running in the browser, tmux keeping the session alive, and the parts that didn't work on the first try.

• 
  Stephanie Hudson (@stepherriffic) reported 11 minutes ago

  @JamesWelbes Yes! But also... Set up a new @Cloudflare account in their behalf. Add yourself as a delegate. At handover, share the main login with them along with instructions to change email and pw. (They will not, in fact, change it, but at least you did the right thing lol)

• 
  Techtitanmb (@techtitanmb) reported 12 minutes ago

  Cloudflare is reporting an unresolved issue affecting its Berlin location. Have you noticed slower websites or connection problems today?

• 
  Sable 🍉 | Playing BG3 (@Sabliano) reported 12 minutes ago

  @NiluarO @Cloudflare I'm having the same issues :/

• 
  Arkfile (@Arkfile_OSP) reported 24 minutes ago

  The irony. Posted a reply on this thread and got the dreaded Cloudflare Turnstile Loop thing again. { @brave / @BraveSupport please fix this! }

• 
  Milk Road AI (@MilkRoadAI) reported 26 minutes ago

  Nvidia just launched a security alliance with over 30 companies and OpenAI and Anthropic didn't join the party. The Open Secure AI Alliance brings together Nvidia, Microsoft, Cisco, Salesforce, Palantir, IBM, Cloudflare, CrowdStrike, Hugging Face and dozens of others to build open source cybersecurity tools specifically for AI agents. The actual trigger for this was a real incident. When Hugging Face got hit with a security breach, its closed AI security tools couldn't tell the difference between the attacker and the defenders trying to investigate so those tools blocked the forensic analysis Hugging Face needed to actually contain the intrusion. Hugging Face had to switch to an open weight Chinese model, GLM 5.2, running on its own infrastructure, to analyze more than 17,000 actions and shut down the breach. That's the case study Nvidia is using to argue closed AI security tools have a structural blind spot. If a defender can't inspect and modify the model doing the defending, they're stuck waiting on the vendor during the exact moment speed matters most. The alliance's core argument is that AI agent security depends on the entire stack like identity, permissions, guardrails, logs not just whether the underlying model's weights are open or closed. Each founding member is contributing a specific piece. Nvidia is open sourcing models and a new agent harness framework called NOOA, Hugging Face is contributing its Safetensors format to prevent remote code execution, Microsoft built a multi model bug hunting scanner, and HPE is contributing zero trust identity standards. Now, why aren't OpenAI or Anthropic in this. This entire initiative is built around open weight models and open tooling as the foundation of AI security, and OpenAI and Anthropic's core business model depends on the opposite, keeping their frontier models closed and proprietary. But to be fair there's also a competitive angle worth naming. Nvidia sells chips to everyone, so it has no downside to championing an open ecosystem where more companies build and compete on top of open models, since Nvidia gets paid on compute regardless of who wins. OpenAI and Anthropic, by contrast, are trying to build durable moats around their specific models and joining an alliance that treats open weights as inherently safer would undercut the entire pitch they make to enterprise customers about why they should pay a premium for a closed, controlled system.

• 
  Ndianabasi Udonkang (@_ndianabasi) reported 26 minutes ago

  @bdkjones @Cloudflare @Apple Ever since I stopped using Cloudflare's DNS proxy, I don't even know when they have downtimes. Most people don't need the proxy service but just use it as default when configuring their records on Cloudflare DNS. For many, DNS proxy is their performance bottleneck but they don't know.

• 
  swisscheese (@swisscheese4299) reported 28 minutes ago

  @OpenAI image generation is still throwing intermittent 520 errors through cloudflare.

• 
  Nate Codes (@Nateemerson) reported 29 minutes ago

  @Steve8708 @tempoimmaterial I’ve got a couple prototypes on deck I’m gonna try this out on. Any word on Cloudflare Worker support as a primary deploy target? I know pages is getting phased out. Gonna try agentNative({ nitro: { preset: "cloudflare_module" } }) which should work in theory 🤞

• 
  Sharan Yalburgi (@sharanry) reported 30 minutes ago

  love @Cloudflare agents infra but why are your workers to so slow to spin up sometimes?

• 
  Mat Diekhake (@thedekeofhazard) reported 31 minutes ago

  Yesterday, I set up Cloudflare for my websites. It made them slow, and I had to turn it off. It also claimed my sites were down at the host several times.

• 
  Publisher in a Box (@publisherinabox) reported 32 minutes ago

  Most publishers will see "charge AI bots to crawl your site" and think revenue. It is not a revenue decision. It is a visibility decision. And the wrong call can erase you from the answers your audience is already reading. Here is what happened. Cloudflare launched pay-per-crawl in July 2025. AWS added the same capability to its firewall on June 15, 2026. Two of the largest infrastructure companies on the web now sell a toll booth for machines, built on HTTP 402, a status code written in 1997 and left dormant for nearly three decades. The background matters. For three decades the deal was simple: let the crawler in, it indexes you, it sends people back. AI crawlers kept the first half and dropped the second. Cloudflare's own data shows training accounts for nearly 80% of AI bot activity. The search-purpose fetches that can actually return a citation are a small slice of what remains. Most of the crawling is pure extraction that sends nobody back. So a toll booth sounds fair. And for certain publishers it is. If you own a deep, licensable archive, a reference database, or proprietary data sets, and your distribution does not depend on those crawlers, charging makes sense. Your content is genuinely worth paying for and you can afford to refuse bots that will not pay. But here is the part the launch announcements leave out. For publishers whose strategy depends on being the answer an AI agent gives, the crawler IS the distribution. Wall it out and you might collect a few cents while deleting yourself from the place where your audience now asks questions. Adobe's 2026 data showed AI-referred traffic to US retailers up 393% year over year. The crawler you would charge and the answer engine that refers a visitor to your site are often the same pipeline. The operator move before you charge anything is to watch the door first. Find out which AI bots actually reach your site and what they take. Separate the ones that feed answers and send referrals from the ones that extract content and return nothing. Then meter one bot on one path and watch what happens to both crawl volume and your presence in AI-generated answers. Let the data inform your policy, not the hype. No public study has yet shown how much citation share a site actually loses by tolling a specific bot. The logic of the cost is sound, but the magnitude is unknown. That is why this stays a decision you make on your own data, not on a rule of thumb. One more thing worth noting for publishers building diversified businesses. Your Facebook page, your website traffic from Google Discover, your newsletter list, and your presence in AI answers are all real audiences with real economics. AI citation is the newest of them and it is growing fast, which is exactly why the publishers who start showing up in those answers now are the ones building an edge before the rest catch on. The operators who win here are the ones already running multiple discovery channels and adding this one while it is still wide open. The toll booth is real. The choice is yours. Before you meter a single bot, know which of them are the ones putting you in front of your audience, and treat your spot in those answers as an asset worth keeping.

• 
  Josh Matz (@joshmatz) reported 33 minutes ago

  @prestonattebery Langchain, Mastra, and Claude Managed Agents. Vercel is close w/ Eve. Flue has Cloudflare deploys. I've thought many times to build it but the "as a service" part to me means people want to deploy on something that's not a side project. What do you want that's not these?

• 
  Techtitanmb (@techtitanmb) reported 33 minutes ago

  Cloudflare is fixing network-performance problems in Istanbul that could affect connected websites and services. Are you noticing unusual loading issues? #techtitanmb

• 
  Lain on the Blockchain (@CryptoCyberia) reported 36 minutes ago

  @Valen_T_N So many major internet outages the last 2 years, more than the previous 28 years I have had on Earth. Amazon store went down for hours a couple months ago, and they held an emergency meeting where they reportedly told devs to stop using LLMs to code because it's sloppa. Cloudflare went down, killing most of the internet. Windows 11 updates have broken devices a half dozen different updates now. Nvidia had to unrelease a driver package, the first time doing so in decades. There are many more examples too of LLMs causing the final product to be significantly worse. The real spooky part is that when you try to name software that was newly made, had features added, or was upgraded in user experience in any way because of the magical power of LLM coding, you literally cannot think of even one (1) example.

• 
  Dylan Garcia (@_dylanga) reported 44 minutes ago

  @CherryJimbo @Checkm3out @Cloudflare I agree. I gave the region fallback feedback to them after their most recent ENAM outage

• 
  Sharan Yalburgi (@sharanry) reported 45 minutes ago

  @Cloudflare worst part is it is impossible to monitor this latency

• 
  Flavio Amiel (@fba) reported 47 minutes ago

  Yet some very pro SEOs here say llms don’t matter. It does matter specially for SaaS in the building space. The strategy is: LLMs recommend you because is free to enter and easy of plug. You might or not upgrade at some point. I’m sticking with resend and cloudflare because if this. And I know the moment I need to upgrade I won’t even flinch. SaaS of the world: fix and keep your .md’s and llms.txt updated.

• 
  DJ Alex Parker (@DjAlexParker) reported 48 minutes ago

  @XBOXSupport Could we get a technical breakdown of the incident? @Cloudflare do it when they have issues and provide lots of detail, would be nice for you to do it too

• 
  Ride The Leaders (@ridetheleaders) reported 49 minutes ago

  @RichardMoglen $NET has one of the strongest weekly bases in $IGV Inference has to live near the user and Cloudflare already owns a 300 city network. The weekly backs it up with a six month base, RS line at new highs ahead of price, handle forming 9% off highs. Undercut and reclaimed the 21ema today while $IGV broke. Earnings in 10 days should resolve the base...

• 
  ₳ndreas (@mrgrauel) reported 49 minutes ago

  @tibor_tee @cursor_ai T-E51116 Same issue with Quad9, Cloudflare, Google as DNS.

• 
  ✞ ꓄ꅐ꒐ꇙ꓄ꏂ꒯ꌦ꒤ꀘ꒐ ✞ (@EvokersShell) reported 52 minutes ago

  Hey, Cloudflare. Suck my fat **** you *****. Let me access the God Damn website Im trying to access so I can set up a ******* server you buncha *****.

• 
  Kamran Khan (@ItsKamranK) reported 53 minutes ago

  @Rian_Visser @Namecheap Rian....worlds best company use Cloudflare for security and speed....if you don't use that's OK....I use Cloudflare CDN for almost every project....I don't have any issue...and why I will pay extra price in renewal charges, if I renew in same flat prices...

• 
  Rovshan (@mrboldpineapple) reported 55 minutes ago

  I still don't get how people merge PRs into main without a real review. I enjoy building with AI, but I read every line. Most of it is fine — but there's almost always some hidden logic worth a second look. Example: I'd never integrated a Cloudflare captcha into an API before. I could absolutely just ask AI to "add cApTcHa, mAkE iT sAfE" and it would work. But then I'd have no idea how my own app actually works, and the bugs pile up fast. So I try to understand every line — and half the time I end up finding a better solution along the way. Yea I'm pretty damn slow, but at least I'm learning along the way and my app is reliable. And features are very expensive, especially if your core functionality is ***

• 
  Yosefu (@OJI_OJI_00) reported 57 minutes ago

  @Spectra010s @Cloudflare By the time you fix that issue, you would have known more about computer networking and how cloudfare works

• 
  2WBIA (@2WBIA_5) reported 57 minutes ago

  @AbuShekauGamer I don't have an issue with cloudflare

• 
  Eric Schweizer (@ericschweizer) reported 58 minutes ago

  @tehseowner @tehseowner What happens if cloudflare flags the domain for abuse complaints though even though it's 100% fake and the links they posted are fake? CF then flags your site as malware without checking or giving you a chance to respond. How do you fix that?

• 
  Josh Pigford (@Shpigford) reported 59 minutes ago

  i'm so confused by @claudeai artifacts. half the time it'll give me a shareable URL. other times it swears that capability has never existing and isn't possible and i should use cloudflare pages.

• 
  Grigori Karapetyan (@GregKara6) reported 1 hour ago

  @Vercantez Absolutely, like support agents and stuff like that, but the article hero says “coding agents dont need vms” This is just me, but i would never use a coding agent thats a regression from current harness tech. 80% of a coding agents correctness and capability comes from interacting with the system, running tests using clis etc. Also for npm install style workflows you said you have a build service, this means you are running this on a VM. I understand that this can be just-in-time or used as needed and saves money, but it adds another layer of complexity for the agent. And there is no shot in hell you are running npm install on s3, s3fs or not. We have been through this road a while ago, and just like everyone else or the industry as a whole have converged on this current architecture. Im genuinely not trying to hate or anything. Just rubs me the wrong way when i see the whole company pushing that stoe of marketing and making posts saying “cloudflare framemogged the sandbox industry” Your article is on point though and you yourself spoke the truth in the first paragraph Always up for tinkering and hacking DMs are open let me know if you want to chop it up sometimes.

• 
  The SaaStronaut | AEO/SEO & Reddit Marketing (@TheSaastronaut) reported 1 hour ago

  Had a $8k/mo client freak out recently bc someone cloned their website, started impersonating them, and was phishing prospects to do God knows what. This clone was ranking page 1 too bc of the name match Client sends the duplicate site to me asking if it was us doing some SEO trick, I said no He said Okay, but was visibly worried This was a rare and unconventional situation And handling client impersonation isn't in a typical SEO's wheelhouse, contract, or scope of work... We had no contractual obligation to look into this or try and fix this But the issue was in search results, and we were the search visibility partner. I saw it as our responsibility whether it was explicitly written or not So, I had the team: 1) Preserve full technical evidence, screenshots, source code, DNS records, forms, hosting details, and timestamps. 2) Sent a takedown notice to the origin host, Omegatech. 3) Submitted abuse reports to Cloudflare and NameSilo. 4) Reported the domain to Google Safe Browsing and Microsoft SmartScreen as an impersonation/phishing site. After our reports, the site was taken down I've done soooo much out of scope work for clients and never ever mention it to them. If you're my client, we're going to take care of you. That's why average client lifecycle with Kingmaker is 2+ years