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

• 
  @meow@femboy.enterprises (@gayasskitty_) reported 5 minutes ago

  @dok2001 @Cloudflare porkbun - cloudflare doesn't support many tlds, it's almost always more expensive for the first year, and i prefer to not have everything in one place

• 
  TKS (@TKS701312296730) reported 6 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.

• 
  tcpdump (@dump_tcp) reported 13 minutes ago

  @kxmcs @Cloudflare Never had issues under high load scenarios if you were to somehow use more ram in my case i never used more then 30gb ram you can also adjust the gc if needed. I tested on 100gbps network card servers

• 
  Top Stock Alerts (@TopStockAlerts1) reported 13 minutes ago

  JFrog introduced JFrog Traffic Controller, a new product that integrates with Secure Access Service Edge providers such as Zscaler, Cloudflare and Netskope to route software package downloads through JFrog Artifactory, where they are screened for security vulnerabilities, licensing issues and quality before reaching developers. The launch expands JFrog’s software supply-chain security platform into the network layer as malicious packages rise sharply, with company research showing a 451% year-over-year increase to more than 171,000 unique instances. RBC Capital Markets also initiated coverage with an Outperform rating and a $118 price target, citing JFrog’s growing cloud business and its role in software supply-chain security and AI-era development. Q2 revenue rose 29% to $163.8 million, while adjusted EPS of $0.27 beat estimates, prompting the company to raise its full-year revenue outlook to $650 million at the midpoint. $FROG

• 
  Cat (@cybersec_cat) reported 14 minutes ago

  Hey Cloudflare, you don’t get to take credit for stopping cyberattacks that came from your own infrastructure. You created the problem. Solving it doesn’t deserve anything but scrutiny.

• 
  vu (@_vu) reported 21 minutes ago

  So if you have a $5 workers plan on cloudflare they think it gives them permission to charge $700+ to your card. After their **** alerts don’t ******* fire and your @cloudflare durable objects turn into ******* billing objects. Honestly ain’t realize how Salesforce coded they were

• 
  christy (@lazarusgpintern) reported 22 minutes ago

  isn’t it ironic that countless amounts of capital and effort poured into agentic payments visa stripe coinbase cloudflare you name it then instinct came along and said **** it we’ll just use human cards

• 
  Impressed keanu (@FN21995) reported 24 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.

• 
  Abhishek (@abhijaazz) reported 24 minutes ago

  I used to trust Cloudflare for WAF now even that feels unreliable 3 times our control plane went down due to CF routing issues. Ughhh

• 
  Mohit Vaswani (@hii_mohit) reported 27 minutes ago

  @bhoomikacodes bc I never tried cloudflare I use spaceship > hostinger > godaddy

• 
  KZZY (@kzzy47) reported 27 minutes ago

  @borrhensaidi A DDoS big enough to take the whole service down instead of degrading it usually means there was no mitigation layer in front yet. Is Cloudflare or similar going in front of it once you're back up?

• 
  Minty (@mintyyyyy7) reported 28 minutes ago

  @4Thunder_Bolt then probably someone used the same vpn server to do something that cloudflare blocked or the website is just blocking vpns in general changing your server will prolly fix it if you didnt already do that

• 
  joker bonito (@abelle_01) reported 30 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

• 
  Abomination (@Abomination81) reported 31 minutes ago

  @DoDeportations Yeah. They have done way more. They are actually changing all of polymarket for them. They first instituted co-location (allowing them to put their servers where the polymarket ones are, giving a huge latency advantage). They opened that to others (non americans) after being caught, but didn't let it be "as good" They reduced delays on takers from 250ms to 50ms for the scammers. They give them 80% rebates, and when asked they ban you from the discord or block you on X. They are now allowing Cloudflare bypass, giving an even extra latency advantage. Its getting so bad. It used to be the top wallets were making 500k... then 1 million... Now the top wallets are crushing it with 10-20 millions in profits and the number of profitable wallets has dropped dramatically.

• 
  deif (@thedeif) reported 31 minutes ago

  One blocker I had with @AmpCode was a large startup cost (5 mins) to a dependent service. Seemed like a waste to make the Orb load it up each time. So instead I used Cloudflare Tunnel to give the Orb access to a VPS with the service running. Now it can smoke test on real data