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 (50%)
• Domains (25%)
• Hosting (25%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	9 days ago
New York City	Cloud Services	28 days ago
Los Angeles	Cloud Services	29 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	2 months ago
Manchester	Domains	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:

• 
  tcpdump (@dump_tcp) reported 1 minute ago

  @kxmcs @Cloudflare Never ran into that big of a ram issue so I guess we will see one day i also many people are using golang around me i never see anyone using rust for anything

• 
  Elia (@eliakuratli) reported 4 minutes ago

  Heydecks talks to models all day. Brand extract, copy, images, re-rolls. Straight to the provider you get no cache, no spend cap, no log when a prompt goes stupid, and one outage equals a dead product. > Everything goes through Cloudflare AI Gateway > Cache the boring tokens > Cap spend so a loop cannot burn the month > Retry + fallback if a provider blinks So if u use AI in your product please try out the @Cloudflare AI Gateway

• 
  Bryan Dubno (@bryandubno) reported 6 minutes ago

  @CloudflareHelp @eastdakota @dok2001 hoping you can help escalate this. Cloudflare has repeatedly charged my PayPal account for a Cloudflare account that is not mine. Support has confirmed the fraudulent charges are tied to an account that I don’t own, but I’m still being told there is no timeline for recovering the funds while engineering investigates payment attribution. I’m trying to get the hundreds of unauthorized charges returned but haven’t been able to get any sort of timeline despite repeated requests over the last 3 weeks. Is there anything you can do to help escalate this further internally?

• 
  Brinkin (@brinkin) reported 8 minutes ago

  @hieuSSR @Cloudflare Damn!

• 
  Tomáš Kafka (@tomaskafka) reported 10 minutes ago

  1. Self hosting a service 2. Having to put it behind cloudflare proxy due to bot attack attempts 3. Now my own server is asking cloudflare whether they deem me worthy to enter every time I try to use it Weird future.

• 
  Sid ™️ (@koomai) reported 12 minutes ago

  Kumo UI is good, but it can't save @Cloudflare from the terrible UX decisions they make to upsell their Enterprise plan.

• 
  lucas (@0xVasconcelos) reported 12 minutes ago

  @ChristoPy_ N usou cloudflare pages = skill issue

• 
  Ajay D'Souza (@ajaydsouza) reported 13 minutes ago

  @MediaRonLLC @cipriangb Better option is to put something like Cloudflare in front of the login. I have a rule that has it under the “under attack” mode for the checks to take place.

• 
  🔻🇳🇿JackWFM🏁🔻 (@Spesh_Alkae) reported 19 minutes ago

  God I ******* hate cloudflare. Trying to go onto warmoth to spc out a guitar and this ****** blocks me. Great. Awesome. @Cloudflare **** you and everything you do you’re useless and I fuming hate you

• 
  Rick Dudley (@AFDudley0) reported 24 minutes ago

  @rehan_shei Do you need help self-hosting? I expect cloudflare will do this no problem.

• 
  Queen Elizabeth II (@ezShroom) reported 24 minutes ago

  @S1NGLEPALEROSE @veculium the whole bot problem is also completely voluntary. she doesn’t want to use cloudflare, most recently because she found a mirror that was hosted on workers and didn’t research how it works, and she also doesn’t want to use anubis because ai contributions like ok so the better option is to just lock a massive % of the internet out and still struggle? bruh

• 
  e_camli (@ekinoks_26) reported 26 minutes ago

  The 24/7 pitch for tokenized stocks is weak if you are a human. Humans sleep. Nobody is buying Nvidia at 4am on a Sunday because they finally can. Put Coinbase's AiFi post next to the stock launch and the two stop looking like separate announcements. x402 crossed 100 million payments by late July, built on the HTTP 402 status code that sat unused for thirty years, now heading into a foundation with Cloudflare. An agent cannot open a brokerage account. It cannot wait for Monday settlement. It can hold a B20 token, post it as collateral, pay per call. Markets that never close were never much of an upgrade for us. They are a hard requirement for whatever keeps running while we are offline. Volume on @base is already tilting that direction. Eight days straight above $1B in DEX volume, second largest onchain economy, and Jesse points at the driver: people earning yield on dollars and borrowing against crypto. Boring flows. Boring is exactly what you can hand to software without supervising it. I might be too early on the agent half of this. Does not change the shape of what got built. The rails are live. The users they were designed for do not read Twitter.

• 
  simon (@xatxat) reported 26 minutes ago

  @biwanczuk Do you know if you'll add support for Durable Object Facets in the future? I think that's the main missing piece to get Cloudflare OS running on celld.

• 
  LokiElGatoQueOpina 🇨🇱🇩🇪 (@lokitoelgato) reported 27 minutes ago

  @PierreJalley @eurofounder Google, Microsoft, Amazon, Cloudflare. If the US decided to shut down those services in Europe, they are lost. Nobody can even work anymore. Wake up. Your continent became the laughing stock of this planet.

• 
  Paul Witcombe (@paulwitcombe) reported 29 minutes ago

  @dhh @eastdakota @Cloudflare I just did a fresh install. Previously I had the Arch - Omarchy install. But now I’ve got a fresh Quattro install which is cleaner. 2 minutes 42 seconds install time which is pretty good for a 2012 MBP Pro. Just had Codex sort out a few wall issues. I’m having so much fun.

• 
  Jeff Escalante (@jescalan) reported 30 minutes ago

  @arturskruze @clerk Really sorry to hear this one. SMS pumping is awful and we put a lot of work and money into preventing it but it still impacts many of our customers unfortunately. Honestly, I recommend now allowing auth via SMS unless you really need to. SMS fraud is very common and perpetrators are relentless. They can inexpensively get through cloudflare turnstile, and will start leveraging other countries even if Italy is blocked 😞 We we try to discount is as much as we are able to, but ultimately we pay the SMS price directly to our own SMS vendors so we have very little wiggle room without us just straight up losing money.

• 
  Donatello | AI, Tech & Wealth (@donatelloinvest) reported 37 minutes ago

  @Cloudflare Performance and security are often treated as separate projects. For a global booking platform, they’re part of the same customer experience. A fast site that fails under pressure isn’t fast. A secure site nobody can use isn’t finished.

• 
  Impressed keanu (@FN21995) reported 38 minutes ago

  The problem of running multiple AI agent instances. Yes — it is already creating a version of that problem, and personal “armies” of agents would make it worse. The internet is a shared commons, just like low Earth orbit. Space junk is leftover hardware that stays up there, collides, and eventually risks a cascade (Kessler syndrome) that makes the orbit unusable. The digital version is a mix of congestion, extraction without reciprocity, and pollution that feeds on itself. What’s already happening Bots now generate the majority of web traffic. Cloudflare data showed the crossover in mid-2026: roughly 57% of HTML requests came from automated systems versus 43% from humans. Agentic traffic (bots that actually click, fill forms, and take actions rather than just scrape) grew thousands of percent year-over-year. One human question to an AI assistant can fan out into hundreds or thousands of backend requests. Multi-agent setups multiply that further. Sites that used to serve a few humans now get hammered by crawlers that walk every link, ignore robots.txt more often, and hit the long-tail pages that never get cached. The result: Bandwidth and compute bills spike (Read the Docs cut traffic 75% and saved ~$1,500/month just by blocking AI crawlers). Servers slow down or go offline for actual people. Cultural heritage sites, open-source projects, libraries, and archives have described it as accidental DDoS. Some have blocked entire countries just to stay up. The old bargain (“you index us, we get traffic back”) is broken. Some AI companies crawl thousands of pages for every visitor they send. Websites are responding with an arms race: more aggressive blocking, proof-of-work challenges, rate limits, and new paid-access schemes for crawlers. The slop / debris layer The second part of the junk problem is content pollution. Generative systems produce cheap, homogenized, often cheerful-but-empty pages (“AI slop”). Other bots scrape that slop, new models train on it, and the cycle repeats. Studies already show large fractions of new websites are AI-generated or AI-assisted, writing is getting more semantically similar and artificially positive, and models trained on junk lose reasoning ability (“brain rot”). This is the closest analog to Kessler syndrome: debris (low-quality synthetic pages) makes the information environment noisier, which encourages even more aggressive scraping of the remaining high-quality sources, which drives those sources behind walls or offline. People have already started calling it “Internet Kessler Syndrome.” Personal armies change the scale Right now the heaviest traffic still comes from a relatively small number of big training crawlers and company agents. When millions of individuals each run their own fleet of research, shopping, monitoring, or coding agents, you get: Uncoordinated, overlapping crawls of the same sites. Agents spawning more agents. No shared “debris mitigation” rules. Higher chance that poorly written or abandoned bots just keep hitting servers forever. The open web starts looking less like a public library and more like a crowded orbital shell full of untracked objects. What it probably does not do It does not literally fill hard drives with undeletable files the way space fills with metal fragments. Digital junk can be filtered, cached better, or ignored. New protocols (agent identity, pay-per-crawl, better preference files than robots.txt) can emerge. Some sites will just become APIs with keys. But the tragedy-of-the-commons dynamic is real: the resource (open, crawlable pages served at low cost) gets over-extracted, quality drops, and access gets restricted. The sites that stay fully open and cheap to crawl become the ones that can least afford the traffic. The space-junk comparison is imperfect but useful. Both are cases where cheap individual launches (or cheap individual agents) impose costs on a shared environment that nobody fully owns. The difference is we can still change the rules of the internet faster than we can change orbital mechanics. Whether we do is the actual question.

• 
  Jon Brown (@jb510) reported 42 minutes ago

  @KatieKeithBarn2 @Mail_Gun @postmarkapp AWS SES. Although I've been wanting to try Cloudflare's new competitor to SES CloudFlare Email Service just to check it out, I've long been happy with SES. I gave up on SendGrid, Postmark, Mandrill, and a bunch of others years ago. I would now never go back to any of them.

• 
  Fiducial.ai (@Fiducial_AI) reported 45 minutes ago

  @Cloudflare Rejection reasons need stable, machine-readable codes. That would let operators fix identity or policy failures without guessing which submission field triggered the block.

• 
  TKS (@TKS701312296730) reported 47 minutes ago

  @MeltsIcy24536 It's clearly the problem because Cloudflare is trying to explain its reasons for failing. The 'genius' needs to get rid of this moronic verification system that's probably locking more legitimate users out of X than it is 'exterminating' real bots.

• 
  RealJBMangum (@RealJBMangum) reported 49 minutes ago

  Cloudflare opens BotBase to bot operators A directory dies if the listed party cannot see or fix their own row. I have built that loop. Cloudflare shipped the operator side yesterday. Status, reject reasons, edit in place.

• 
  Cole Leavitt (@MomentMai) reported 50 minutes ago

  @dump_tcp @Cloudflare This is the dumbest thing I’ve ever heard, golang is a GCed language and never the less the scale of how CF operates would cause more harm than good to use golang

• 
  GZ Lin (@gzlin) reported 51 minutes ago

  7/8 Two answers fit this physics. Ship continuously in public: Chrome ships two security releases a week, the kernel defers fixes at most seven days. And put protocol layer mitigations live while the real fix lands. Cloudflare did that for Log4shell in 2021.

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

  @cosmovjtcjt @Cloudflare @CloudflareHelp Hi Zak - do you have a case open or a support ticket number?

• 
  Xavier Rivera (@XavierRiveraX) reported 57 minutes ago

  Microsoft disclosed TerminalFix, a ClickFix variant that uses fake Cloudflare CAPTCHAs to trick users into running a malicious command via Windows Terminal or PowerShell instead of the traditional Run dialog. The chain uses DLL sideloading and a custom reverse-tunnel implant giving attackers persistent network access. Fix: restrict PowerShell and Run dialog execution via AppLocker or Group Policy, and enable PowerShell script block logging. Source: Microsoft/The Hacker News.

• 
  Pranav Bansal (@prnvbn) reported 58 minutes ago

  @Cloudflare Damn, all the clippy warnings make sense now

• 
  joker bonito (@abelle_01) reported 58 minutes ago

  I use Hostpinnacle for domains, good customer care service. Cloudflare for the records such as DNS and MX. Vercel for lightweight web applications

• 
  Armand K. (@krrypton) reported 58 minutes ago

  @colearendt_ @RueNahcMohr Doubtful for it to be site-specific. I've been getting this **** from CloudFlare on at least 4 different sites, including this one.

• 
  Bilal Bakr (@bil0090) reported 59 minutes ago

  @maxktz @cursor_ai I think CloudFlare is/was down which is causing some problems