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 (43%)
• Cloud Services (32%)
• Hosting (17%)
• 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
Istanbul	Domains	2 days ago
Greater Noida	E-mail	5 days ago
Paris	Domains	6 days ago
Crisfield	Domains	7 days ago
Noida	Hosting	11 days ago
Augsburg	Domains	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:

• 
  RazorSharpFang (@RazorSharpFang) reported 5 minutes ago

  @acvalensVT German law being applied to American companies in such a roundabout way is wild. The fact that Cloudflare - maybe the biggest Internet backbone - is delegating complaints decisions to a foreign nation to the company being hosted is awful.

• 
  Johnmark Obiefuna (@jayhemz) reported 8 minutes ago

  Proxying through Cloudflare solves almost all Wordpress security issues.

• 
  Transform Labs (@TransformLabsHQ) reported 11 minutes ago

  4/ If Cloudflare can automate this aggressively at their scale, you have zero excuse. The tools are already commoditized, the playbook is public. Any 2026 hiring plan that assumes human support scaling is already outdated.

• 
  Pravobzen (@Pravobzen) reported 12 minutes ago

  Using a vendor-specific messaging platform (i.e. Discord, Slack, etc) to support users, build a community around your software project, and use LLM agents is not an ideal solution and I'm surprised Cloudflare hasn't picked up on this, given their push to reinvent everything.

• 
  Ryan K 🌥 (@Yank) reported 16 minutes ago

  @elreyuso2 @Cloudflare sorry to hear about the frustration. have you opened a case with support and received a case number I can look into?

• 
  Cadence Agyirey 🇬🇭🏳‍⚧ (@kubedoll) reported 18 minutes ago

  Why push toward a 5 figure homelab? Because my friends and supporters can help pay my electricity and cloudflare bill in exchange for their own shared cloud, and there's really no limit to the number of 10W mini PCs i'm willing to rack if i can use the spare compute.

• 
  Focus $EDGE (@focus_edge) reported 19 minutes ago

  @dotkrueger @Cloudflare can't get my login mail

• 
  Ryan Daigle (@rwdaigle) reported 19 minutes ago

  @ritakozlov @Cloudflare Great stuff. Would love aome way to bind/tunnel a browser instance to a local URL or service binding so it can operate on non public URLs while still being secured via the normal CF service to service security model. Any options for that use case?

• 
  Marc Campbell (@marccampbell) reported 19 minutes ago

  @uday_devops only cloudflare unless it’s one of the few tld they don’t support yet

• 
  Ash Nallawalla (@ashnallawalla) reported 20 minutes ago

  @gaganghotra_ Great reminder. Most geo-blocking plugins and CDN rules need a specific exemption for known crawler IP ranges. Cloudflare and Wordfence both support this, but it's rarely enabled by default — so it's worth checking even on sites that seem to be working fine.

• 
  LukeYoungblood.eth 🛡️ (@LukeYoungblood) reported 20 minutes ago

  @curtjg1971 @Cloudflare We put in a limit request Monday but still no resolution. They have really good service otherwise, but I hope the people handling limit increases are eventually going to resolve it.

• 
  Darren *I upset people* Richardson (@S0UNDK1LLAH66) reported 20 minutes ago

  @RyanNoKneel @2LivesCid Down detector did show X as a haphazard line. So if it’s all over the place - there’s problems. It’s a main spike you gotta watch out for if a line goes straight to the top. Then check Cloudflare on same app. It’s Friday. So maybe expect some O - o.

• 
  Ashish Rawat (@eashish93) reported 21 minutes ago

  There's literally 100's of bugs regarding rsc and vite on vinext (a next.js alternative for cloudflare). Past 1 week, I filed more than 15+ issues, but the good news team is very quick on resolving those issues

• 
  Fozzy (@fozzydiablo) reported 22 minutes ago

  cloudflare is my number one holding based on the theory all vibe code would be edging I never knew what this meant but smart people told me about it. So I decided to host my app backend on cloudflare tech is amazing but ended up being the complete opposite of what I needed lol

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

  @MarkZofMarkZ @Cloudflare I call it experience. You might have a bad experience but it won't make any service garbage

• 
  Paras (@buildwithparas) reported 29 minutes ago

  @samlambert 20% feels small until cloudflare has an outage and you find out how many of your tools sit behind them

• 
  xo jig (@xojigsx) reported 29 minutes ago

  @BorowskiKamil @TheDealMakerGuy @grok Does Cloudflare issue invoices through Polish KSeF?

• 
  Merlin (@TheWizardTower) reported 34 minutes ago

  @Ruff681368 If improper use isn't obvious, it's hiding a bug. The point of an abstraction is to make invalid states unrepresentable, and improper use obvious. This is what Rust/Haskell/Scala do by using Maybe/Optional instead of a universal null type. Even when CloudFlare had the outage because they called .unwrap() on a pointer, the meaning of that function is "You solemnly swear that this is a Some(x), because if it's a None, I'm blowing up your runtime." And, indeed, when that came up, the problem was *immediately* obvious. The go code in question here was code that looked reasonable at first glance, but wasn't. That's a problem!

• 
  Bree Sharp | Local SEO Strategist (@bree_sharp) reported 36 minutes ago

  After moving MWOV from SiteGround to Cloudflare: Ahrefs went from returning 1 URL per crawl to crawling the site normally. The culprit was LiteSpeed's bot management — aggressive enough to rate-limit Ahrefs into giving up after the first URL. GSC showed 59 pages indexed fine. The problem wasn't the site. It was the layer between the site and the crawlers. Sometimes the issue isn't your content or your configuration. It's your infrastructure making decisions you don't know about.

• 
  Jeffrey Orr (@Jorr98944493) reported 37 minutes ago

  @JustExoticss Debounce your sign-in button so one click can't fire 50 requests, and throw Cloudflare in front with a per-IP rate limit on the login endpoint. That alone will stop the spam from eating your API budget and buy you breathing room to deal with the actual 550/min cap.

• 
  Pollux {x} 🐻🪝☀️🇺🇸 (@Pollux2789) reported 38 minutes ago

  @ArgusForge @Acquired_Savant Cloudflare sucks! @evernode actually fixes this kind of stuff. Check them out. You could maybe build something decentralized cloud instead of centralized clouds $EVR But by telling by all your work overall I’m sure you’ll correct your team and make them better. Keep up the work!! 👊🏻

• 
  kitcatixoxo || Margaritamar (@Caddue) reported 39 minutes ago

  btw the problem seems to be cloudflare and many apps suffer momentarily

• 
  Phil Eaton (@eatonphil) reported 39 minutes ago

  In terms of the cost savings: Cloudflare network error logging takes up a big chunk in production. Switched all icons to svg (saved a good deal) then merged them into a single sprite which compresses better. Minifying JavaScript for the first time. And started paginating articles

• 
  Gerrard (@leaohut) reported 45 minutes ago

  @JeffScottDev @Cloudflare They fired over a thousand people and according to Reddit most of the support team got obliterated. No one is responding to my tickets either

• 
  whatnicktweets (@whatnicktweets) reported 48 minutes ago

  @boristane DO VPS => Never Cloudflare => Daily

• 
  Prince S.A. Adewole (@Samuel_Aadewole) reported 48 minutes ago

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

• 
  Udit (@uditbatra1990) reported 51 minutes ago

  [quoting since can't reply to @levelsio] there's a middle ground that worked well for me. 1) add an extra "billing email" on whichever service allows it (eg. aws, cloudflare) 2) set up auto forwards to this billing email based on subject + sender for whichever service doesn't allow it you have to remember to do it *once* per service, and you end up w/ an email inbox full of just invoices

• 
  Leo 🏴‍☠️ (@leostera) reported 55 minutes ago

  @DanniFriedland true! i have a little repo where an agent manages ansible provisioning for my local service and its such a relief from having to do this manually. literally just asked it to make a new postgres instance setup with ssl, and configure cloudflare access+tunnel -- 5 minutes later i got a hyperdrive db!

• 
  Shekhar (@cshekhar) reported 58 minutes ago

  @daytonaio runs containers, which share one Linux kernel across tenants. Vulnerable. The container boundary itself was not breached. The shared kernel underneath was. Patched in 12 hours. Credentials rotated. Signups paused. @Cloudflare also runs containers on their own edge. Shipped a kernel-level filter within hours. Kernel patches in five days. No customer-facing exposure advisory ever published.

• 
  Pyromonkey ⛏️🔥 (@Pyromonkey360) reported 59 minutes ago

  @SentientTtv the issue rn is that if cloudflare falls everyone will switch to the qr code google thing, so it might be wise to get rid of that first