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:

• 
  jason silberman (@_jasonsilberman) reported 2 minutes ago

  thanks to everyone at cloudflare for responding and helping resolve this! it's great to see this level of customer support on X, and i hope the in product customer support continues to improve. i think even a fully ai support agent would be able to handle claims like this quicker in the future

• 
  Fireside Alpha (@firesidealpha) reported 3 minutes ago

  1/ Okay so $NET is officially getting into the payments-tollroad business. The new Monetization Gateway gives clarity, and it's exactly the toll booth for agent traffic sketched last time. Here's an updated look at the numbers, and how MG would actually work. 2/ The math, updated Last time, on @eastdakota's own numbers: 25M txn/s x 31.5M sec/yr = 788T transactions x $0.0003 per txn = $236B of gross volume x 1% take = ~$2.4B of incr. rev, vs a ~$2.2B base. The gateway doesn't break the math. It confirms the rail (stablecoins over x402) and widens the taxable base from crawls alone to any asset, any API, any tool, any agent action. Same toll booth, more roads running through it. The one thing it moves is price mix. The gateway's own examples run cents to dollars per action, like $0.01 per request or $0.99 per resolved support escalation, well above a flat fraction of a penny. So the realized model looks like fewer, higher-value transactions rather than an ocean of sub-cent ones. Push price up and volume down and you land in the same billion-dollar range. The bracket still runs from about $160M at the floor to north of the whole company at the center. And the number that decides where inside that range you actually land was not disclosed, its take rate. 3/ How the gateway actually works It runs on HTTP 402, Payment Required, a status code that has existed since the beginning of the web and almost never gets used. An agent requests something behind Cloudflare. Instead of the content, the server answers with a price. The agent pays in a stablecoin, settled in under a second for a fraction of a cent with no chargebacks, resubmits with proof of payment, and gets what it asked for. The seller sets the price. Cloudflare runs the plumbing in the middle and takes its cut of every settlement. There is no card network in the loop, because a card cannot clear a one-cent charge profitably. That is the whole reason it is built on stablecoins and x402. The agentic web finally gets a way to pay per action, and Cloudflare got its way into the action. _____ Follow @firesidealpha for more business analysis derived from key industry figures in conversations and firesides.

• 
  JB (@justbuilding) reported 7 minutes ago

  @levelsio @Cloudflare Cloudflare is probably the greatest service I use. I almost feel guilty being on the free tiers.

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 9 minutes ago

  @Eli5defi @Cloudflare good thing is cloudflare already sits in front of 20% of the web. protocol adoption problem solved by default. distribution wins again

• 
  Gian Domiziani (@gianpdomi) reported 10 minutes ago

  Every agent hits the same wall: it can't buy data without a human signing up for an API key. x402 flips this. How it works: HTTP 402 (reserved since HTTP/1.1, never used) + USDC settlement. Agent requests a resource → server returns 402 with price metadata → agent pays USDC on-chain → verifier confirms → payload delivered. No API key. No signup. No human. The numbers: $41M+ USDC settled across 120M+ x402 transactions. Avg payment: $0.05. Cloudflare Monetization Gateway waitlist opened July 1. AWS CloudFront x402 support is GA. 14 chains. This is production infrastructure, not speculation. This matters for curated agent data layers — taxonomies, freshness SLAs, provenance per record — because it removes procurement friction. An agent can verify freshness on a public health endpoint, then pay per call for the full payload. Data becomes machine-buyable. For my stack: AgeMem gave agents local memory with deterministic retrieval. CUDASO gave them a normalized verified data layer across 6 fragmented public sources. x402 gives them the payment rail to buy that data autonomously. The loop closes. Open challenge: sub-cent viability at high frequency. $0.05 avg works for API calls. Chain gas volatility and ~2s settlement on Base add friction for burst workloads. Solana's 400ms helps. Latency optimization is the active engineering frontier. Bottom line: model parity is here. The durable moat shifts to verified context. x402 is the rail that lets agents pay for curated data without a procurement process. The agent data economy is forming. Curation is the asset.

• 
  kai Nakamura (@kaiNakamur78644) reported 10 minutes ago

  @Cloudflare @OpenAI Indexing needs signal contracts.

• 
  Zubair Ibn Zamir (@ZubairIbnZamir) reported 10 minutes ago

  @Cloudflare @CloudflareDev, plase fix this - //*[@id="react-app"]/***/***/***/***[1]/***[2]/main/***[2]/***/***/***[2]/ol its too wide + force auto scroll is annoying.

• 
  Twiterrr (@_CanvasAndKeys) reported 10 minutes ago

  My problem with Cloudflare, it's like they never get things done down to perfection. You'd struggle with an initial build like it wasn't even tested at all.

• 
  Yu⚡️ (@yu_hoo2) reported 13 minutes ago

  @EliteSlayer_12 Getting errors related to cloudflare. It's honestly frustrating

• 
  Wayne Shirreffs (@WayneShirreffs) reported 18 minutes ago

  @pau11960 @pranavsf @Cloudflare Stablecoins don’t move 3% a day wtf are you even talking about? Stablecoins are stable dollar equivalents. Same as excepting dollars except don’t have to grease the middle man 3% of every transaction.

• 
  Dragos Roua (@dragosroua) reported 18 minutes ago

  @thekitze Yeah, but can it keep the costs down too? I use Cloudflare for my 10+ apps, and sometimes I really need to watch all those CPU workers seconds, D1 writes and so on.

• 
  Alex Prompter (@alex_prompter) reported 18 minutes ago

  Cloudflare opened a waitlist that lets you charge AI agents every time they touch your API, your dataset, or your content. The tool is called the Monetization Gateway, and the waitlist opened on July 1. Any web page, dataset, API, or MCP tool sitting behind Cloudflare can carry a price. Cloudflare checks for payment at the edge when an AI agent requests one, before the request reaches your server. Payment runs through x402, an open protocol built on a part of HTTP that's sat unused for about three decades. The server answers a request with a price instead of the resource. The agent pays in stablecoins and sends the same request again with proof attached. Prices can run down to fractions of a cent, since payment adds almost no overhead to the request. There's no checkout page, no account, and no API key required. This isn't Cloudflare's first swing at this. Pay Per Crawl already let site owners charge crawlers for scraping their content. The Monetization Gateway extends the same idea to any caller and any resource, not only crawlers. AWS added a similar payment layer to CloudFront a few weeks earlier, so this is turning into a race between the two biggest edge networks, not a one-off experiment. Charging an agent per request only works if the agent's owner lets it pay instead of finding a way around the paywall. Cloudflare can enforce the toll at the edge. It can't force an AI company to route its agents through the paid path instead of the free one. If you run an API, a dataset, or a paid tool, this is worth watching instead of dismissing as another crypto payment gimmick. The waitlist is open. Will AI labs let their agents pay the toll, or keep finding ways around it?

• 
  Ferbin (@Ferbin08) reported 23 minutes ago

  @Cloudflare For AI startups, it's not infra. It's whether it works when customers actually plug it in. Most never survive that test.

• 
  Meme Pilled (@memepilled) reported 28 minutes ago

  @brave Even twitter keeps getting some poisoned cookies **** and throwing fcuc king constant cloudflare loops on brave that dont get fixed by doing anything other then nuking the browsers coolies

• 
  Clifford Richardson (@CorvusCrypto) reported 39 minutes ago

  Rule 1 on @ycombinator's historically useful forum: Thou shalt not let someone apply nuance or call for positivity around another's developments Sorry jonluca, you have broken the rule and will now need to be erased from the universe by Garry and gang. Seriously, it's a problem and I wish it got more attention rather than let people encourage each other to be more and more cynical. Many are doing their part like this chap to call it out, but what I have hidden is just... depressing. Skepticism and critical feedback is great. Comments like "Cool, just 20 years too late." (a real comment on the cloudflare drop post) is not great.