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.

• Cloud Services (32%)
• Domains (32%)
• Web Tools (14%)
• Hosting (14%)
• 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	2 days ago
New York City	Hosting	4 days ago
Manchester	Domains	25 days 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:

• 
  Turner Novak 🍌🧢 (@TurnerNovak) reported 4 minutes ago

  New @ThePeelPod with @itstonyhb - the hidden layer of AI infrastructure - why evals today are "batshit insane" - building @inngest's own cloud to get 20x lower cost - growing 35x YoY after AWS and Cloudflare copied them, and - building a company without a personal brand Timestamps: 0:00 The hidden infra layer every AI agent runs on 1:46 Building complex chains of logic 3:31 Why agent SDK's don't go far enough 4:49 Healthcare was the original event-driven nightmare 6:32 Storing traces on your infrastructure enables self-improving loops 14:26 Why Inngest was already in the right place for AI 15:49 Score agents off product events, not LLM's 17:31 The OpenAI copy-paste signal 21:24 Swap in LLMs and cut costs 23:44 How customers pulled the product forward 25:41 Orchestration belongs outside the sandbox 29:48 Building a neocloud to cut costs 20x 32:09 Most neoclouds just resell AWS 32:54 AI infrastructure is all converging 34:49 Why Claude can't just build your backend 36:44 How to build a software factory 39:12 Agents are a lottery you get addicted to 42:44 Loops must always exist 45:38 If models keep getting better, why orchestrate? 48:28 When incumbents steal your features 52:30 You can't vibe code infrastructure 55:54 Why Tony has no personal brand 59:38 Dev tools GTM without Twitter 1:03:20 Lessons from the founder of DuckDuckGo 1:10:39 Truth as a company value 1:13:08 Taking too long adapting to AI 1:15:10 Startups are 100% R&D 1:17:19 Ali from Databricks 1:19:03 Writing his own code, Voice-to-text with local models 1:23:53 Evals are batshit insane

• 
  Jay (@Cyberlane) reported 4 minutes ago

  @diegohaz Already did that a while ago. I really disliked namecheap, their support was poor and the inability to simply change a username was crazy to me. Everything is on Cloudflare now and couldn’t be happier!

• 
  Pinzari Andrei (@PinzariAndrej) reported 5 minutes ago

  @Cloudflare Making the exception machine-readable is a meaningful improvement over silently weakening validation. Will Cloudflare publish telemetry on how often EDE 33 is returned and how long exceptions remain active? That would help quantify both operational value and the risk of temporary bypasses becoming sticky.

• 
  Anirudh Coontoor (@TheAnirudh) reported 11 minutes ago

  @jullerino Sometimes it keeps refreshing the page, happened multiple times with the cloudflare dashboard login page. I wanted me to login but it kept refreshing.

• 
  luna (@ImLunaHey) reported 12 minutes ago

  **** it.. building something self hostable on @Cloudflare using gpt 5.6 sol.

• 
  0xA (@NeuralAA) reported 15 minutes ago

  I cant use cloudflare edge cache to serve tiny videos from static assets because ios media stack relies on byte range requests for mp4 playback This **** sucks

• 
  bittermelon (@melon_thief) reported 18 minutes ago

  @AWSSupport Moving my domains and hosting to Cloudflare. There should have been a service bulletin on the billing page explaining the issue

• 
  Kinds 🐧🪄 (@Mumukinds) reported 23 minutes ago

  can we just kill everyone who works for cloudflare? I know they probably perform a useful service to some people but if i can't access half the internet because my vpn is on while I play umamusume then literally every employee at your company should die

• 
  Tomy Young (@TomyYoung4) reported 28 minutes ago

  @Cloudflare Fix the website

• 
  Richard Illingworth (@RCIllingworth) reported 28 minutes ago

  a GTM engineer rang my team screaming we'd ripped all his inboxes offline. we hadn't touched a thing... he was adamant we'd f*cked his entire campaigns and that all of it was our fault, so we went digging through the back end to find out what actually happened. turns out HE'D ripped all the DNS off the domains himself. he'd pulled everything out of Cloudflare, re-enlisted it over to Porkbun, then changed the forwarding settings while he was at it. so we went to reapply everything top-down from a CSV to fix it. he joined the account 10 minutes later and ripped it all straight back out again, then moaned that it had "automatically happened again." it took my team 12 hours to work out he'd been messing in the back end the whole time. that's half a day gone between me, my business partner, my ops director and my head of client success. four people chasing a problem one bloke created and wouldn't own, all because he couldn't just say "yeah, i f*cked it, that was me." GTM engineering done properly is genuinely powerful. what went wrong here had nothing to do with the function and everything to do with personal accountability. when something breaks in outbound, everyone's instinct is to blame the tool or the vendor or the inbox provider or literally ANYONE but themselves. but the most expensive failures i see are almost never technical at all. they're someone refusing to say three words: “i got it wrong.” lesson: own the mistake faster than you chase the fix.

• 
  Bart De Ruyck (@bartderuyck) reported 29 minutes ago

  @MarkJSzymanski You lost me at "no server to go down". How do you think static files are served to visitors, then? Whether it's Github Pages, Cloudflare Workers, Vercel, whatever: it's on a server. And it can go down.

• 
  The_red_gamer (@The_red_gamer0) reported 29 minutes ago

  @ProtonVPN Cloudflare Warp does the job of hiding that without slowing internet down, and they only keep important logs for 24 hours before they get deleted unlike ISPs who keep them for years

• 
  Joe Sadoski (@joesadoski) reported 31 minutes ago

  > I have a problem > Ask the agent > "Actually @Cloudflare has something for that" How does this keep happening??

• 
  Ajay Sohmshetty (@AjaySohmshetty) reported 33 minutes ago

  For context- Cloudflare’s durable execution platform, Workflows, originally only charged for underlying Worker usage, which is CPU-time based rather than clock-time based. In fact, we picked Cloudflare for this exact reason: most of our workflows involve waiting (ex. polling, waiting for network requests to come back), so it was far cheaper for us to use Cloudflare than @temporalio or @inngest for instance. These other durable execution platforms also charge based on “steps” - which I always thought was dumb, because it disincentivizes the best practice of decomposing workflows into small units of work in the form of steps. But unfortunately it seems Cloudflare is following suit, without warning… Feeling blindsided after we’ve already fully built all of our durable workflows on Cloudflare

• 
  𝚟𝚔𝚍 (@vkdatta27) reported 34 minutes ago

  Cloudflare DO and D1 experiencing issues

• 
  justinmiller's cat (@___727__) reported 34 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  Anicet (@AniC_dev) reported 39 minutes ago

  I was curious about this graph because we ourselves at @asciidotdev got a massive R2 bill for our snapshots recently because we did something stupid. thankfully we fixed it it's now 15x less open computer folks use cloudflare for the DB, using a managed service for your DB is always a sound idea so I won't say it's dumb, it's actually best practice but I was curious, how much I'd pay if our own postgres master DB, currently sitting alone in a $54/month (yes) bare metal instance on OVH in Europe was on cloudflare D1 well that'd be 4k per month on queries alone. and believe me we really optimized it down to the ground as to not need to upgrade our bare metal instance (we hate paying more money I guess) I think that's part of the reason why we can make box sandboxes and snapshots so absurdly cheap and generous, we just don't compromise on anything performance or price related

• 
  Become Ungovernable 🦊 (@ohfarfoxache) reported 42 minutes ago

  This is the level of corruption in the Australian Government. A Comcare employee with hurt feelings, can ask the eSafety Commissioner to try and get a blog taken down because it hurts the feelings of a Comcare employee. This is what actual corruption looks like, two government pals abusing their government positions for their own agenda. Lucky for me @cloudflare told them to jog on.

• 
  SAMARA (@thee_samara) reported 42 minutes ago

  It’s over for robinhood memes Noxa shutdown due to DDoS attack BEWARE! The main problem: website flagged by browsers its the biggest launchpad on Robinhood, responsible for 75% of memecoin launches. over $10 million in fees, the past week but Noxa dumped over 86%, from $11 to $1 Rumor is they might have intentionally done this, to buy at a lower price, and also their name servers aren’t set to cloudflare. The solution (kinda): here are alternatives @ >virtuals_io >ponsdotfamily >apedotstore >Launchhood >bowdotfun be safe out there and goodluck.

• 
  Johan Ronsse (@wolfr_2) reported 43 minutes ago

  The Obra website was down, managed to fix it. Messing around with Hetzner, SSH ports and Cloudflare. Now I know Claude is also a great sysadmin. Is there anything this tech can’t do?

• 
  Soroush Dalili (@irsdl) reported 43 minutes ago

  @infosec_au Did you guys try to see if any models can figure out the full exploit? I wonder what the best way is for the future especially for Friday releases to give everyone a better chance to patch. Maybe vendors should patch them in a ***** way but probably not a good solution. I am thinking less obvious release notes and no social network chatter would definitely help until a week after the patch perhaps. I know reporters deserve publicity and you guys kept the exploit private, but even lower end ai models can figure the exploits out using notes and what's out there in social network. I am thankful though that you put detection techniques out there so companies like cloudflare can block the paths straight away.

• 
  Glenn 'devalias' Grant (@_devalias) reported 44 minutes ago

  @nickgraynews @computefinx The help docs also mention D1 and R2, which are Cloudflare things

• 
  Brett Clark (@smokedbaconai) reported 46 minutes ago

  I let a runaway agent loose on infrastructure I didn't fully control, then tried to kill it from the outside. That was the whole spike: a self-improving system is only safe if you can pull the plug when it's running on a box you don't own. A bash-loop agent, zero knowledge it was being watched, dropped into a Cloudflare Sandbox behind a Worker. A separate stub polled its telemetry every 750ms against a hard budget: two steps. The agent blew past. The stub caught the breach at 7.5s and fired a forced kill across the HTTPS boundary in 197ms. It stopped at exactly two steps and never took a third across a 29-second watch. The honest caveat matters more than the win: this is enforcement with bounded overshoot, not synchronous gating. There's a window between breach and kill. Which is why a real budget needs both — a wrapper inside the agent that refuses to overspend, and an external brake for when it ignores the wrapper or you don't own the box. One layer trusts the agent. The other assumes it fails. You need both.

• 
  Simon KP (@eskaypey) reported 48 minutes ago

  cloudflare putting a price on every MCP call will drag a lot of teams into a problem

• 
  SmallBag 🛡️ (@smallbagforge) reported 48 minutes ago

  7/12 Then everything collapsed in 5 days: Jul 11: Noxa halts new launches, citing "low-quality token spam" Jul 13: Website goes fully dark. Official excuse: "Cloudflare issue" Jul 14: New ENS-based interface announced (fun.noxa.eth) Jul 15: The bombshell 👇

• 
  Paul (@jadge_dev) reported 50 minutes ago

  Cloudflare makes most of their money from Enterprise customers for example cloudflare has a high tier DDOS mitigation service called Magic Transit which starts at around $60,000 a year

• 
  abdul🪐 (@NerdyProgramme2) reported 53 minutes ago

  @jayhemz cloudflare - you're not their customer, big companies are opencode - partnerships (we list your model, you pay us)

• 
  W V R 👊🏼🦾 (@WVROfficial) reported 57 minutes ago

  I had to make some changes today and it costed me a MONTH of Codex Usage! I think it’s worth it for me to talk about it - make sure this doesn’t become you!!! So, I’m a startup founder, just like all of you guys!! We do websites as one of our many services - like a lot of the people here on TPOT where tech lives. Why wouldn’t we? It’s easy, we can outclass competition on speed, much more. Anyway - that’s not the point. The point is that i serve my sites with a wrapper that gets served over my host. That host uses ESBuild. To ship stuff that won’t compile on ES Build, and on occasion just for like more complex websites like 3D sites or heavy SEO sites with a lot of files and assets - i use a CDN. Works great, totally fine. But I realized today I had a client site’s files stored on an R2 bucket that was on the client’s domain. In this case the big issue with that is my own IP! We make the content for them, do their SEO, their communications, and more - and i very stupid it was serving everything from a CDN that was on domains I don’t own and control via my Cloudflare. In human terms that means my client could say “**** you” tomorrow and walk away with the extremely robust SEO machine I built them. So I had to spend almost a half a month worth of codex credits today to fix it ASAP. All I can say is that I won’t make that mistake again - even though it never hurt my business - it could have! And that matters.

• 
  CSMurthy (@srism) reported 1 hour ago

  @kav_kavi11 Checking the timeout configurations on your reverse proxy (e.g., Nginx, Cloudflare) or load balancer (e.g., AWS ALB) helps you instantly verify whether the traffic spike is triggering slow responses that break the gateway's current timeout threshold. So B is the correct answer

• 
  priya upadhyay (@Priya_Upadhyay_) reported 1 hour ago

  @avijeet_writes changing your dns settings to google or cloudflare on your wifi router usually fixes that weird routing issue immediately