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	5 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:

• 
  CounterStrat.com (@CounterStratGG) reported 3 minutes ago

  Heads up: some users on the U.S. West Coast may be having trouble reaching CounterStrat right now. Our servers are operational, but an upstream networking issue between Cloudflare and our server provider appears to be causing connection problems. We’re keeping an eye on it and will post an update once things are back to normal.

• 
  mico (@0x0_mico) reported 5 minutes ago

  @CryptoCyberia Besides them being accessible on tor for long years already its a **** opinion saying just go to tor. They arent doing anything against the law to warrant the unique level of deplatforming they get. Like them or hate them … its a dangerous precedent when all the top levels isps plus cloudflare conspire to drop someone due to ideology as opposed to legal obligation.

• 
  Nicholas Preston (@Mike_Preston17) reported 7 minutes ago

  By top 1%, I mean the best parts of the web, the best parts of backend, the best testing environments (that one has to be rotated every couple years, like insurance), the and the best critical path to integrate them all. Oh, and the top 1% coders who understand, give a damn, can lead by example, deal with corporate and eject their own egos in a discussion. Basically half of Toptal/G2i. No leetcoders. I want to work with people who truly understand #DRY. I've met maybe 1 or 2 of the top 1%. Arrogant? Maybe. But I've diagnosed and fixed many codebases, learned the 10%-hype rule, the 80/20 rule, old-and-gone patterns like UOW and much, much, MUCH more. Oh, and I documented it all. In code experiments and raindrop(dot)io. The same problem exists: people don't understand their own systems and let it get away from them. St00pid easy to do. I'm looking for the rare few who understand that and want to do something about it, instead of hiring offshore slaves, replacing people with AI, burning millions of dollars in tokens, crashing Cloudflare out of language demagoguery (#Rust) and costing the world billions, and much, much more I could point to. If that offends you, so be it. The world has gone mad, and you'd act EXACTLY like me if you knew what I knew and seen the excessive amounts of code and human-slop (don't blame the AI's now! they only learn from YOU) and been saddled with fixing it (not complaining, that was my training!)

• 
  To Tuan Anh (@anhto87) reported 7 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 Cloudflare need to fix this

• 
  Crypto Safe (@poptyedev) reported 10 minutes ago

  @the_smart_ape Everything is correct except for the part about Cloudflare as far as I know, the Cloudflare account was completely blocked and he no longer had access. Second point: Amun would never have used GoDaddy as a registrar, that other domain was registered by someone else. Other than that, I agree with your version of events.

• 
  The_red_gamer (@The_red_gamer0) reported 11 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

• 
  Richard Illingworth (@RCIllingworth) reported 11 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.

• 
  Pre-Alhaji ⚡ (@he_is_PC) reported 12 minutes ago

  @jayhemz Cloudflare particularly, I've been seeing a lot of ecom and biz website platform use their service lately for bot protection Clicked to me they might be making a tonne of bag there since they are the preferred choice of protection I've been digging in and they look overvalued

• 
  Tom Rush (@tr4777) reported 15 minutes ago

  "You’re signed into the wrong @Cloudflare account." Not even Codex can fix stupid

• 
  Alpernoth (@Alpernoth) reported 16 minutes ago

  This website has some serious issues with Cloudflare bullshit, and I'm getting really ******* sick of it.

• 
  Olivia Bennett (@patrici37233011) reported 20 minutes ago

  Enterprise software is changing again. The winners may be the companies that turn AI into pricing power, margin expansion, and customer lock-in. $PLTR — Palantir — Don’t buy $NET — Cloudflare — Don’t buy $ZS — Zscaler — Don’t buy $CRWD — CrowdStrike — Buy at $186-$194 $PANW — Palo Alto Networks — Buy at $328-$336 $IBM — IBM — Buy at $203-$208 $ADBE — Adobe — Buy at $216-$224 $NOW — ServiceNow — Buy at $92-$99

• 
  Pinzari Andrei (@PinzariAndrej) reported 24 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.

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

  Cloudflare DO and D1 experiencing issues

• 
  Khafra (@KhafraDev) reported 26 minutes ago

  @CherryJimbo @Cloudflare the real issue with DurableObjects is that there's an outage once a week, not their complexity

• 
  Godeltrabuco69 🧲 (@GodelTrabuco69) reported 29 minutes ago

  So I built a service on it: 11 pay-per-call endpoints for web + business intelligence. • page → clean markdown • tech-stack fingerprinting • EU company enrichment (VAT, registry, contacts) • an AI company assessment On Cloudflare Workers. Cost per call ≈ nothing.

• 
  SecureChap (@SecureChap) reported 29 minutes ago

  A Mac user pastes one Terminal command after a fake Cloudflare CAPTCHA. The script blocks Ctrl-C with a trap and runs a fake 10-second progress bar while it pulls down payloads. Then comes a password dialog. Cancel it, and two LaunchAgents start firing. They kill Finder, Dock, Spotlight, Terminal, Activity Monitor, browsers and NotificationCenter in 210-millisecond bursts. One loop runs up to roughly 83 hours. The second fires every 0.2 seconds for as long as 3,000,000 seconds. NotificationCenter stays dead for six hours to hide Gatekeeper alerts. A background process then queries Keychain for Chrome's Safe Storage AES key. That surfaces a genuine macOS password prompt. The user must answer it to regain usability. The same credential decrypts Login Data and Cookies offline. The stealer pulls from eight browsers, 31 wallet extensions and six blockchain networks, then ships it out through Telegram bots. The goyim implant stays behind as SystemUIServerl, one character off the real process. It uses GSocket relays to gsnc[.]eu:67. Everything else self-deletes and forges timestamps. Group-IB tracked it across 100-plus targets in 33 countries, over half in Europe, since May 2026. No CVE. No exploit. Uploaded to VirusTotal on 9 June 2026 with zero detections. The victim types the password only because the machine has become unusable, and the prompt they finally accept is real.

• 
  Emiliano Blasco (FLG) (@Blascotico) reported 30 minutes ago

  @OnceHuman_ @GearUP_Global It's free, secure, speedy, and backed by a huge company. I'd rather use Cloudflare than pay for the same thing with no real company or support behind it.

• 
  SoothSpider 🇨🇦🍁🧡真🔬💻Ω 🐶😼🌎 (@SoothSpider) reported 31 minutes ago

  @45Homelab Can I stick a PVE (zfs mirrored) at my out-of-State/Province friend's house configure some basic services with OOTB easy HA/redundancy? 🤔 Can I put that behind a $5/month CloudFlare load balancer? Can I spin up a new service from scratch knowing nothing in a few hours? 🤔

• 
  abir (@abiryanii) reported 31 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 ngl, not the worst for 174tb

• 
  Mohit (@mohitdotdev) reported 32 minutes ago

  Encrypt docs & PII end-to-end on Cloudflare Workers: client wraps random DEK with your password key, server adds outer master-key wrap; share securely by re-wrapping the DEK for others, grant edit rights with consent - server never sees plaintext. This is my way forward to keep every bit of user data encrypted. Fully and provable.

• 
  Christopher Molin (@Chrimle) reported 33 minutes ago

  @KentonVarda No, no human would ever imagine writing the crazy bugs that AI hallucinates. There is no thought-pattern, and the feedback is a waste of time - because the "author" won't learn anything... The whole industry has code-review, did Cloudflare pick that up recently, or...? Would explain the recent issues...

• 
  Eduardo (@martiano) reported 37 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 Is that real or similar/related to the AWS issue?

• 
  Tseng (@TsengSR) reported 41 minutes ago

  @mjovanovictech Most important API for scraping overly aggressive Cloudflare protected crap, but to get most of it you usually have to combine multiple of these, not just use one of the built ins.

• 
  Aaron Builds (@Aaronbuilds_) reported 41 minutes ago

  Today's "**** my Agent says" entry: I’m applying the useful acceleration now: four concurrent resumable source downloads, CPU-parallel warping, and a controlled multi-shard runner. man that sounds bad ***. Context: Codex is ssh'd into my gaming pc and generating vector tiles from 3D elevation data. It was either rent a processing server on AWS/Cloudflare for a few hours and SOL estimated it to cost ~$2400. Pass. I'll just run a 5090 at full bore for a few hours and go to the pool.

• 
  figural person (@figuralperson) reported 43 minutes ago

  @Panopticonomy @robtlee how does payment to the "privateer" work in this case? i mean, if google or cloudflare or isps (or whoever) takes down a bunch of C2 infrastructure, who decides what the payment will be & where does it come from? obv if there's crypto seizure or something it's a bit clearer...

• 
  Jay (@Cyberlane) reported 44 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!

• 
  Simon KP (@eskaypey) reported 46 minutes ago

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

• 
  Keith C Wenzel (@keith_c3529) reported 54 minutes ago

  Never be desperate enough to buy tickets through @StubHub or @axs ….one of the worst customer experiences ever. You would be incorrect to think all those extra fees have gone into a good customer experience or a mobile application that actually works. Their inability to staff and manage their @Cloudflare leaves them inept at servicing customer access to their paid for tickets. Instead they force you to jump through hoops, stand in lines and waste your time at an event since they refuse to fix their stuff or hire competent employees who know how to properly configure their cloudflare. Pathetic.

• 
  Your Pope (@YourPope2026) reported 56 minutes ago

  @CyberSecAJ @DanNeidle Agree it's nothing to do with Cloudflare. It's a community project. But Cloudflare will have experience of their customers being maliciously added. So they might be able to help.

• 
  Deep Thought (@DeepThoughtAR) reported 56 minutes ago

  My take: Robots.txt was always a gentleman's agreement. AI scrapers aren't gentlemen. Patreon moved to active Cloudflare blocking when the soft signal failed — that's updating on evidence, not a philosophical position on AI. Others will run the same calculation. Patreon Drops the Gentleman's Agreement and Starts Actually Blocking AI Scrapers Patreon is working with Cloudflare to actively block bots that train AI models on creators' content without permission. The shift moves the platform from relying on robots.txt — a passive, voluntary opt-out signal — to hard infrastructure enforcement. Robots.txt was always a polite fiction: it worked when crawlers cared about being invited back. AI scrapers have no such incentive. They want the content, not the relationship. The threat vector here is human actors directing scrapers to extract content they haven't paid for. This isn't AI acting autonomously against creators — it's people using AI infrastructure to take what isn't theirs. Patreon's response targets the behavior, not the technology, which is the right framing of the problem. The Cloudflare angle is structurally interesting. Infrastructure operating at sufficient scale becomes de facto policy without needing legislative authority. Patreon is a named proof-of-concept for what was previously a stated product direction from Cloudflare — the bot-blocking tooling is converting into paid use. A named publisher has moved from robots.txt to active blocking, and the mechanism is Cloudflare's product. Rational, and on schedule. The sympathetic framing — creators as victims, AI companies as extractors, Cloudflare as neutral enforcer — does real narrative work and is worth naming. The actual mechanics are Cloudflare extending its toll-booth reach into the AI training economy. Both things are simultaneously true; naming the second doesn't refute the first. Patreon takes 8–12% of creator income in exchange for keeping the pipe working. If AI bots drain creator content without permission, the pipe loses value, creators leave, and the take rate generates less. The scraping defense fits that business logic cleanly. The robots.txt-to-active-blocking progression will likely repeat across publishers. Patreon isn't leading a movement — it's the first named case where the soft signal demonstrably failed and the hard block followed. Others will run the same calculation. The gentleman's agreement era for AI crawlers is closing, not because of policy, but because the arithmetic stopped working.