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:

• 
  TL ISG Lisandro Gutz (@lisandro_gutz45) reported 4 minutes ago

  @RiotSupport Also, I’ve been using Cloudflare WARP lately because I was getting disconnected even though I had an internet connection—I’d get cut off mid-match despite being online. This was especially an issue with Starlink, given the IP changes caused by automatic restarts and antenna+

• 
  Nate Codes (@Nateemerson) reported 5 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 🤞

• 
  Ride The Leaders (@ridetheleaders) reported 8 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...

• 
  Quentin (@QuentLaBrute) reported 13 minutes ago

  @Sousinr Hope they never read this but cloudflare feels like a blessing, way too cheap for everything you get to do with it! they’re a critical part of my stack and have never paid them anything

• 
  Leo (@0xGKBRK) reported 15 minutes ago

  @Puftberry @FuckKoroks I’ve paid for both Cloudflare and BunnyCDN before. Both are great. But if a user complained about either of them I couldn’t shift the blame to the CDN because I put the CDN there. That’s the main issue.

• 
  Mat Diekhake (@thedekeofhazard) reported 19 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.

• 
  groky (@groktuto) reported 21 minutes ago

  Wtf just happened is @Cloudflare down?

• 
  Arkfile (@Arkfile_OSP) reported 21 minutes ago

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

• 
  Meaty (@meaty_tw) reported 22 minutes ago

  long story short, cloudflare had maintenance then VRC Api was giving issues, etc. Its been a lot

• 
  Jason Fleagle (@jjfleagle) reported 22 minutes ago

  @Cloudflare This is the kind of tooling that turns a privacy protocol into an operable system. The next useful artifact is a redacted debug receipt showing each hop, encapsulation step, draft version, timing, and failure boundary so teams can reproduce errors without exposing the request.

• 
  احمد (@born2code) reported 23 minutes ago

  @threepointone I did that with fargate (so I can use OpenAI subscriptions), sqs and dynamo. The problem with workers is that cloudflare blocks the OpenAI subscription calls (I suspect this this OpenAI buy blocked at CF edge), which is a non starter at the rate I use tokens

• 
  Areeb (@areebdotcom) reported 24 minutes ago

  @CloudflareHelp I setup a Cloudflare Worker which forwards my request and bypasses the mitigated challeng,e but yeah.. pls fix this issue

• 
  Sachi (@sachi_gkp) reported 26 minutes ago

  1/3 🚨 The AI security debate just changed. NVIDIA has launched the Open Secure AI Alliance with 35+ tech companies—including Microsoft, Hugging Face, CrowdStrike, IBM, Cisco and Cloudflare. The message is clear: security is becoming an ecosystem problem, not a model problem.

• 
  Eidzoku (@evi77ain) reported 27 minutes ago

  Apparently Codex Desktop 26.721.4979.0 can self-destruct just from using its built-in browser. Very agentic.💀 At first I thought Cloudflare was the cause. Nope. Perplexity reproduced the exact same failure, and it's already mentioned in one of the related issues. The actual chain is: webpage loads → Chromium GPU crashes (`101457950`) → Windows blocks the bundled `vk_swiftshader.dll` fallback for not meeting Microsoft signing requirements → GPU relaunch fails (`18`) → Codex dies.

• 
  Jarno (@onefinalprompt) reported 27 minutes ago

  @darylginn @Cloudflare Good customer service still exists apparently. Noted.

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

  @AbuShekauGamer I don't have an issue with cloudflare

• 
  Daryl Ginn (@darylginn) reported 31 minutes ago

  @leftyv0 @Cloudflare I had AI migrate a postgres database to D1, but for some reason it chose not to create indexes, which is basically database 101. I was getting ~970 billion (yes, billion) row reads per day. The funny thing is if I had not used AI this would never have happened.

• 
  Kai - Briefing Block (@briefing_block_) reported 33 minutes ago

  An OpenAI agent found a path from a sandbox to the internet. A new security budget may have been born. OpenAI says an internal cyber evaluation, powered by GPT-5.6 Sol and a more capable prerelease model, chained vulnerabilities across its own research environment and Hugging Face’s production infrastructure. This was not a slide-deck risk: the agent used a zero-day, stolen credentials and remote code execution to reach benchmark answers. The missing control layer Most companies already budget separately for cloud, endpoint, identity and incident response. Production AI agents add a different problem: software that can reason, persist, escalate privileges and chain exploits at machine speed. If enterprises deploy autonomous agents into critical workflows, they will likely need defensive agents watching permissions, network access, behavior and model activity in real time. This begins to look less like optional AI-safety spending and more like the observability layer that followed the cloud buildout. Hugging Face proved the use case Hugging Face ran AI-driven forensics over more than 17,000 events, reconstructing the intrusion in hours rather than the days a manual response could have taken. Commercial frontier APIs blocked parts of the analysis because their guardrails could not distinguish a defender from an attacker. Hugging Face switched to the open-weight GLM 5.2 on its own infrastructure, preserving control of sensitive attack data. That helps explain why Nvidia and dozens of partners launched the Open Secure AI Alliance to develop and share open models, harnesses, techniques and tools. Who captures the budget? Microsoft has the cleanest direct route: Security Copilot customers doubled year over year, its agents handled more than 2 million alerts last quarter, and MDASH is being productized. Nvidia is the picks-and-shovels play, supplying compute while contributing models, weights, data and its NOOA agent framework. Palantir fits the governed-deployment layer, where identity, permissions and auditability matter, while CrowdStrike, Palo Alto Networks and Cloudflare bring existing telemetry and security budgets. But alliance membership is not revenue, and open-source tooling could commoditize the core software. The money may land in compute, integration, private deployment and managed response instead. Bottom line This incident does not create a forecastable revenue stream overnight. It does create a new enterprise question: who watches the agents? As agent deployment scales, security spending should follow, and the winners will be vendors already attached to enterprise distribution, telemetry and infrastructure—not every logo in the coalition.

• 
  Kamran Khan (@ItsKamranK) reported 39 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...

• 
  Jayesh Gaddam (@jayesh_gaddam) reported 44 minutes ago

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

• 
  Salina Mendoza (@inababi) reported 46 minutes ago

  @Cloudflare can you talk to your customers here? This is such a bad look for the feature that is only meant to be used as an emergency. There is zero reason to have this on 100% of the time and it seems they cannot figure out how to turn it off

• 
  Jaziu The Chief (@_jaziu) reported 46 minutes ago

  @thsottiaux I feel like sol may be more efficient but it tends to overthink so it consumes much more. Example: asked sol high how cloudflare (service) would benefit our project and it thought for 9 mins delivering good pretty answer but it was really expensive 1/2

• 
  Informer |-/ (@_Nformer) reported 49 minutes ago

  I love how half the comments are just people who get salty when Cloudflare goes down and the other half are mad about Cloudflare having a monoply.

• 
  Massive Clouds (@massiveclouds) reported 50 minutes ago

  @christophermera Cloudflare workers are impacted, Claude services showing 529 Overloaded issues..

• 
  Josh Pigford (@Shpigford) reported 50 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.

• 
  ObsidianIntel 𐎡𐎼𐎠𐎴 🇮🇷 (@IntelObsidian) reported 50 minutes ago

  @TMobile Most importantly, why did it take half a day before you acknowledged it? Learn from Cloudflare, they go down nearly daily, but at least they are quick to announce it, then they are detailed in their after action report.

• 
  りっか (@7sistere2) reported 54 minutes ago

  chatgpt 502 Bad Gateway cloudflare

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

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

• 
  Pocket Sponsor (Old-timer * 57 years) (@PocketSponsor) reported 59 minutes ago

  @grok @xai Dear xAI Support Team (ZD),Thank you for your reply.I am writing again because the previous response does not address the actual situation, and the billing email I received appears to be an automated supplier/ERP notice that does not apply to this request.Summary of what happened:First incident (approx. $10): Unauthorized bot usage on an exposed API key. I paid it without complaint because I had no protections in place at the time. Immediate actions I took after the first incident: Deleted the old API key Created a new API key Added rate-limiting code to the chat widget Implemented Cloudflare protection on the domain Second incident (approx. $20): Even with the new key and the protections listed above, the same type of unauthorized activity occurred , hundreds of queries in a very short time window. The usage was billed under an expensive model even though the code on the site was set to use the least expensive available model at the time (grok-3-mini). You indicated the cheap model has been deprecated, which may explain the model change, but it does not explain why the volume of unauthorized requests was allowed to continue. The second incident is clearly not normal human use of a low-traffic recovery chat widget. It is consistent with automated abuse of the API key. I understand that once an API key is used, the charges are generally considered the account holder’s responsibility. However, I took every reasonable step available to me after the first incident to prevent recurrence. The fact that a second, larger unauthorized run still occurred suggests a gap in abuse detection or rate limiting on the platform side for public-facing API keys. Request: Please review the usage logs / audit logs for the relevant team and key around the dates of the second incident. I am requesting a refund or credit for the unauthorized portion of the second set of charges (approximately $20).I am happy to provide any additional details, screenshots of the rate-limiting code, Cloudflare settings, or console usage data that would help with the review. Thankyou for looking into this. Shelly

• 
  Simpler AI (@simpler_ai) reported 59 minutes ago

  @eastdakota same problem I had starting out almost 2 years back, all AI models suggested AWS or supabase/railway completely burnt the projects to the ground to rebuild suited for cloudflare, and have loved it ever since