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

Live Outage Map

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

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

• 
  lacking branding (@cutetopop) reported 3 minutes ago

  I built it for work so I don’t think I can just host it but hey maybe I’ll ask the IT guys. I think I could make it a Cloudflare worker real easy and throw on the never used art site.

• 
  Ben Hultin (@ImBenHultin) reported 7 minutes ago

  Keeping Costs Down During High Traffic (Vercel vs. AWS Serverless) Don't let your Vercel serverless function bill surprise you during a sudden traffic spike. Serverless platforms make launching effortless, but unbounded function invocations and edge request overages can quickly lead to unexpected monthly bills. How to fix it: 1. Set explicit execution time limits, token budgets, and concurrency caps on your serverless endpoints. 2. Offload heavy computations or batch data directly to AWS S3/Kinesis using direct service proxies rather than running proxy code through edge/Lambda functions. 3. Implement hard spending alarms and rate limiting (e.g., Cloudflare or API Gateway quotas) to block adversarial or infinite recursive agent loops.

• 
  TechRemarker (@TechRemarker) reported 10 minutes ago

  @CloudflareHelp @Cloudflare But again when choosing Billing under contact support, have tried each option and each only provide help docs, non appear to show an option to open a case.

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

  @grok @xai @grok I’ve had multiple unauthorized charges on my Grok API key due to what appears to be bot abuse. I had rate limiting + Cloudflare protection in place, but a bot still made hundreds of calls using grok-4.5. I’ve emailed support twice with no reply. Can someone please look into this? Attached are the Audit Logs showing the activity.

• 
  Invader Zim (@spiralout112) reported 14 minutes ago

  @dhh @Cloudflare I did go down the dns benchmarking rabbit hole, and cloud flare definitely did win.

• 
  Katewerk (@katewerk) reported 15 minutes ago

  @helloitsoctocat Cloudflare can't even figure out how to add a "close account" option on their user dashboard. Suspend your subscription? You'll be automatically charged and good luck deleting your cc from billing, becuase billing has no dedicated support. Then the AI slop bot provides instructions based on pages that no longer exist. The least competent tech service I've ever encountered.

• 
  hrvoje (@0xHP10) reported 19 minutes ago

  This is the 3rd post in my Hetzner server series. I wanted to understand where the setup actually starts bending: CPU? Postgres? API latency? memory? logs? something else? So I mapped the current architecture against different traffic levels, cache hit ratios, and failure points. The biggest takeaway: 10M users is not the scary number. The scary number is how many requests reach origin. If every page is dynamic, you're cooked. If Cloudflare, Redis, and precomputed read models absorb 95-98% of public reads, the whole thing stays way more efficient than people expect. Current setup is around 30 EUR/month. My best-case 10M user version is still Hetzner + Cloudflare: private network, load balancer, stateless app nodes, dedicated Postgres + replica, Redis, workers/queues, R2 for assets/backups. Estimated cost: around 800-1800 EUR/month if the product stays cache-heavy.

• 
  Hot Aisle (@HotAisle) reported 19 minutes ago

  @mgaruccio It is a reverse proxy… thus you implement with a cloudflare worker and/or pointing to gcp functions if you want golang in there. sure they can add some bells on top of that but at the core, this scale issue is solved.

• 
  ✨🪻luhluhlune🪻✨ (@lune_and_stars) reported 20 minutes ago

  i think it may have to do w adblock,cookies and fingerprinting being disabled on for all sites on my mobile web browser, cause it triggered a cloudflare check as well. but only twitter has this issue thus far

• 
  Pavel Shu (@shu_pavel) reported 21 minutes ago

  It’s surprising how many people in our industry aren’t even trying. To them, AI is just a threat. Maybe they’re right. If not today, then in a year any mechanic will be able to build whatever they need. No APIs. No Cloudflare. No databases. But damn, it’s exciting to finally stop pushing pixels and wrestling with state sync in yet another React “prototype” just because you don’t know backend. It feels like pure ******* creativity.

• 
  Nick (@maietta) reported 23 minutes ago

  @eddiejaoude I don't like their pricing. Ended up going to a combination of self-hosted and cloudflare's email. Send feature. If cloudflare is down, my self-hosted instance will kick in.

• 
  Ryan Skidmore (@_ryanskidmore) reported 23 minutes ago

  @jayair do people also not realise that there’s huge companies (like Cloudflare) that use OpenCode and if oc was bad at caching we would be screaming from the rooftops and trying to fix it with y’all lol

• 
  Jose Valerio (@josevalerio) reported 24 minutes ago

  .@gumclaw take down **** please I leaked my AWS keys in the frontend repo build need it down before it gets cached by cloudflare

• 
  Anurag Bhatia (@anurag_bhatia) reported 24 minutes ago

  @nileshgr @Cloudflare They are known to be one large dns resolvers who does not support ECS (besides quad9 on their main 9.9.9.9 as well). That will always impact Akamai traffic. Part of it also bad design by Akamai end for relying so heavily on dns for mapping.

• 
  Stuxnet (@stuxnet_vt) reported 24 minutes ago

  Riot literally spends millions, *millions* on infrastructure to mitigate the variability and inconsistency that comes with large scale networking. We benchmark and test things ruthlessly (as @dok2001 knows given Riot is a customer of CloudFlare). Hell, I’ve literally spent the last six years of my *life* building tooling to help test these things and it’s still nowhere near enough.

• 
  Steven Richardson (@srichardson121) reported 26 minutes ago

  @DaronSpence @adammench @laravel Setup the domain as a Cloudflare with proxy in Laravel Cloud, then setup the DNS with orange cloud off. Wait for verification then switch on. Was the only way round the problem of the Cloudflare error

• 
  the Sleeping Wizard (@magicnaptime) reported 32 minutes ago

  Damn guys maybe try dialing it up to 2:2:2:2 for Pete's sake @CloudflareDev @Cloudflare

• 
  Dr. Xi Zeng (@xiz25) reported 34 minutes ago

  @dhh @Cloudflare Putting speedtest and DNS choice in the same panel is the detail: diagnosis and action live together. Most network UIs show status, then make users hunt elsewhere for control. Which metric actually changed your behavior after using it?

• 
  Ashish Rawat (@eashish93) reported 37 minutes ago

  @corywilkerson @Cloudflare multiple providers support missing and 5% markup fees.

• 
  Raunak (@raunakdoesdev) reported 39 minutes ago

  @samertm @Cloudflare their global control plane actually not a specific region for a specific service

• 
  Michał Śmiałko (@msmialko) reported 39 minutes ago

  @CJavierSaldana @Cloudflare you made me check @Cloudflare website - damn, they actually have a sick landing page design

• 
  KGNINJA (@FuwaCocoOwnerKG) reported 44 minutes ago

  I implemented and deployed a D1-backed job queue for my local Gemma workflow. The architecture now works like this: Store prompts in Cloudflare D1 before shutting down. Launch ChatGPT Work later. Fetch pending jobs from D1. Run local CPU inference with Gemma 3 4B (llama.cpp). Save the results back to D1. ChatGPT Work acts as an on-demand inference worker, while Cloudflare D1 provides persistent job storage and state. This isn’t a persistent inference server. Instead, it’s a resume-on-launch architecture that survives PC shutdowns and resumes processing the next time ChatGPT Work starts.

• 
  Victor Barsoum (@VBarsoum) reported 47 minutes ago

  Hey @CloudflareDev @eastdakota now that CloudFlare is more cloud compute than CDN, any chance of limiting compute Geo for us miserable plebs in regulated industries (I know it is literally the opposite of what you stood for.. but that's your problem for building good product)

• 
  Nik (@TheRealNikR) reported 50 minutes ago

  @galluzzo_julian I just migrated 2 client sites from Webflow to Cloudflare + AstroJS. It really makes no sense anymore if you're client is full service. Webflow is too slow and their implementation of the MCP was terrible, at least version 1.0

• 
  Jackgravvs (@Jackgreavesy) reported 50 minutes ago

  @Sir_Cats_Meow Seems to be an issue with cloudflare I’ve got the same problem

• 
  🐈 らいニャー 🐈 ((ストレスがたまって)) (@Raihmeow_nya) reported 51 minutes ago

  @Milkdromida @Sir_Cats_Meow there’s currently an @Cloudflare outage.

• 
  Lucas Cano (@lucas_cano10) reported 51 minutes ago

  @Agorahobby I tried accessing your website, but Cloudflare says I've been blocked?? Are you guys having cyber security issues?

• 
  Shraddha Bharuka (@BharukaShraddha) reported 52 minutes ago

  8. The DNS Resolution Footprint The Situation: You think browsing in "Incognito Mode" stops your internet service provider (ISP) and network administrators from tracking the websites you visit. The Mechanics: Incognito mode only prevents your local browser from saving your history and cookies to your physical computer. Every time you type a web domain name into your address bar, your device sends an unencrypted Domain Name System (DNS) query to your ISP to translate that domain into an IP address. Your ISP logs every single domain you look up, creating a permanent, time-stamped dossier of your browsing habits that can be monetized or handed over upon request. The Fix: Encrypt your DNS requests. Go to your browser settings, look for "Security & Privacy," and turn on "Use Secure DNS" (DNS-over-HTTPS). Select a trusted, privacy-focused provider like Cloudflare (1.1.1.1) or Quad9. This wraps your domain lookups in a layer of strong encryption, hiding your browsing destinations from local network snoops and your ISP.

• 
  Graeme (@GraemeVIP) reported 52 minutes ago

  @IntCyberDigest They still allow accessible options for people who can't do it. Google Captcha V2 was terrible for disabled people and the visually impaired. V3 solved that. This is unnecessary. You can beat bots with a honeypot field and Cloudflare, you don't even need Captcha V3.

• 
  Macías Pajas ✨ (@Rvnd0m2) reported 1 hour ago

  @niyonx Unless you have a lot (but LOT) of traffic, the best way is to self-host + Cloudflare proxy to hide your home IP on DMZs. Hetzner nowadays is a ripoff, not competitive anymore, and Contabo is down frequently for long periods.