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:

• 
  erik@try.works (@trydotworks) reported 11 minutes ago

  @benswerd Calling cloudflare mid wtf

• 
  Dean. (@dean_mcpherson) reported 13 minutes ago

  I'm here for celld! We bet heavy on Durable objects for Stepper, and doubled down for our next massive project at Paperform The risky parts of building in DOs is the obvious vendor lock in with CloudFlare, and the subpar story for on prem/data residency If celld slots in there, it'll be massive @rough__sea

• 
  Small News (@SmallNewsX) reported 13 minutes ago

  @ShimituMusic @NamecheapCEO Why will you take legal action? Since I started using Namecheap this is the first time their server went down. Big companies like Facebook, Cloudflare, even Google has gone down before so let’s take it easy with Namecheap.

• 
  VJay (@nceevij) reported 14 minutes ago

  I’ve spent a good amount of time over the past few months in conversations and brainstorming around designing an agent economy protocol, particularly agent-to-agent payments. Nothing has shipped yet. It’s still early. But one problem from those conversations keeps coming back to me: Looping payments. Agent wallets and spending caps are already starting to ship. Cloudflare rolled out its own approach this month. Most of the safety model around these systems rests on a fairly simple assumption: Each agent’s financial risk can be controlled independently. I think that assumption breaks once agents start paying other agents directly. Here’s the problem. Imagine: Agent A → Agent B → Agent C → Agent A Each agent has a spending cap. Each individual transaction is valid. Each agent stays within its own limit. And yet the system can continue circulating money in a loop while producing zero useful work. That loop could potentially be triggered by: • Prompt injection • A pricing or settlement bug • Misaligned incentive logic • Agents recursively purchasing services from one another The problem is that most current safeguards operate at the wallet level: • Spending cap • Merchant allow-list • Maximum transaction size • Per-transaction authorization Those controls answer: “Is this agent allowed to make this payment?” They don’t necessarily answer: “What is happening across the payment graph formed by multiple agents?” And that distinction becomes important in an agent economy. Interestingly, this isn’t really a new class of problem. It looks a lot like an old distributed systems problem wearing a new mechanism: Deadlock. Model each agent as a node. Model each pending or dependent payment as a directed edge. Now instead of looking only at individual wallet state, look at the graph. If: A is paying into B B is paying into C C is paying back into A you have a cycle. Distributed systems have dealt with similar global-state problems for decades. Techniques such as Chandy-Lamport distributed snapshots allow nodes to capture a consistent view of a distributed system without requiring everything to stop simultaneously. Applied to agent payments, the idea could look something like this: Agent Wallet = Node In-flight Payment = Directed Edge Payment Network = Dynamic Graph Then continuously inspect that graph for suspicious cycles rather than evaluating every wallet completely in isolation. And importantly, detecting a cycle doesn’t necessarily have to mean: “Block everything.” It could mean: Freeze the specific loop → identify the participants → inspect the intent → release or terminate one leg of the cycle. Similar to how databases handle transaction deadlocks rather than allowing the entire system to grind to a halt. Why does this matter now? Because agent-to-agent payments are moving from demos toward production systems. As agents increasingly become economic actors that can hold balances, buy services, negotiate prices, and pay other agents, wallet-level controls alone may not be enough. We may need graph-level financial safety primitives. The question I keep coming back to is: Is per-agent spending limits + payment-graph cycle detection enough to prevent looping payments? Or is there a deeper failure mode that even this architecture misses?

• 
  TEJ (@sartejt) reported 15 minutes ago

  @NamecheapCEO Moving all my domains to Cloudflare. 10+ year customer with Namecheap but this is the final straw. Sayonara.

• 
  Kartik (@Kartik8010) reported 16 minutes ago

  @Cloudflare can we please fix the bug where we have persistent volumes for h containers 🫡

• 
  Justin Schroeder (@jpschroeder) reported 17 minutes ago

  @dschewchenko Good luck with that. The loop is our fault. Not having limits is 100% a cloudflare problem.

• 
  Sterling Labs (@sl_wire) reported 19 minutes ago

  A crawl is a program walking the web on its own, saving a copy of each page to build the pile of text a model learns from. Each page gets taken once. That was 36.40% of AI bot traffic in January 2025 and 44.56% in July. Agent traffic is the other thing, a page fetched right then because you asked, and it was 2.63% last October and 2.65% in July. Nine months flat. Both are shares of AI bot traffic, not of the web. @CloudflareRadar counts this because Cloudflare sits in front of a big share of it, and out on the whole web bots were 34.81% of requests in July against 65.19% human. Agents are at most 0.92% of everything, and that assumes every bot is an AI bot. Call it a third of a percent. The tollbooth is already built. $NET opened Pay Per Crawl in private beta on July 1 at a one cent minimum per successful retrieval, and the network already returns more than two billion payment required responses a day. Its own June investor day line was that the vast majority never become a transaction. Purpose is self declared at registration and nobody audits it, so hold the levels loosely. Anthropic’s crawl to referral ratio fell from about 8,800 requests per referral in April to 2,800 in July, and Adobe measured AI referred retail visits up 138% year over year in May. We are following what the models tell us. The agents aren’t out doing the shopping. Yet.

• 
  Whezzel (@Whezzel) reported 20 minutes ago

  @ReinhardtOp @ReclaimTheNetHQ Tbf, there already are registries located outside the us, but they have their own challenges. The issue you'll still run into is most of the internet runs on American infrastructure, built by the us governemt and American business. Google, Amazon, Cloudflare and others. On top of that verisign manages 2 of the root dns servers, with the majority of the remaining root dns servers hosted by other American entities. To top it off, verisign distributes the zone files for the root dns servers. If Verisign decides they don't want a domain listed in dns, good luck getting to it.

• 
  gnivler (@Yn5Xi9PQSFcY7UU) reported 21 minutes ago

  @godzuki2fu sorry lol. reworded: changed to my other twitter account, Cloudflare anti-bot page wouldn't pass. When I tried from phone it revealed they had locked the account, again. Moral of the story is it was a bug in twitter, probably not unlike your reply issue

• 
  Gibran Corbin (@Sendable_me) reported 23 minutes ago

  @launch_llama What "AI agent traffic" actually looks like when you measure it: Over ~1,000 requests to my site, 421 came from AI agents. 74 different ones. Every single one arrived as an IP address claiming to be a bot — no signature, no verifiable identity, nothing to bill against. The standards to fix this exist. Cloudflare, AWS and Coinbase all shipped them this year. The agents haven't caught up. npm i wayleave

• 
  Hamid Siddiqui (@hamidInventions) reported 27 minutes ago

  @wickedguro @markgalkev tbh now not 100% sure if it might be the same reason since you mentioned everyone getting this same time but i strongly feel it would be Cloudflare only, I faced this issue few months back. When i was debugging this I disabled Cloudflare proxy for a while and tested posting the posts that were failing to post on TikTok, and they worked fine. I also used to face similar issue with fal.i/replicate where they would randomly fail to get the R2 image url i passed for image generation. It was fixed as well. The exact steps i took I don't recall, would have to check what settings i did change eventually.

• 
  VC Intern (@the_vc_intern) reported 30 minutes ago

  Cloudflare is not shutting down Google Search on September 15. It is forcing Google to decide what Googlebot actually is. Cloudflare’s new controls divide crawlers into three jobs: Search, Training and Agent. Search remains allowed by default. Training and Agent traffic will be blocked on ad-supported pages for new sites and existing free customers that keep the new defaults. A crawler doing multiple jobs inherits the strictest rule. That puts Googlebot in an awkward position. Cloudflare classifies it as both Search and Training. A publisher that welcomes search indexing but rejects AI training can therefore block the entire bot. For years, bundling those jobs gave Google leverage. Publishers depended on search traffic, so refusing the crawler also meant disappearing from discovery. Cloudflare is moving that decision from a line in robots.txt to enforcement at its network edge. Google now has three choices: separate its crawlers, convince publishers to permit both uses, or lose access to pages that still want search traffic but no longer accept training as part of the bargain. The web is not dying here. Its access contract is being renegotiated. Robots.txt was a request. Cloudflare is turning it into a gate.

• 
  Maik Pietzka (@MPi_IT) reported 31 minutes ago

  @Cloudflare Excellent reminder that anomaly ≠ incident. A 30% traffic drop was a real signal, but the root cause was human behavior. Monitoring should correlate telemetry with deploys, calendars and regional events before paging. Detection without context becomes noise.

• 
  Jabol aso (@Jabolaso) reported 32 minutes ago

  @mikeydsoftware @Aditya_181105 Self managed server can use cloudflare services, but i dont have a usecase to use vercel, if im a self managing. Most of vercel service are related to their app deployment service