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:

• 
  Pikanou ⚡🏴‍☠️ (@pikanou_) reported 1 minute ago

  Agent Experience is quite a terrible label since AI doesn't have, urgh... feelings. So repurposing human-centric 'UX' terminology for autonomous agents is weird and just plain buzzword. Sounds like AX is the new UX! Rebuild everything! But behind the scenes, the engineering is a big reality. For now most websites are hostile to AI agents, quite difficult for them to visit the pages with cookies banners, cloudflare bot challenges, client-side JS hydration crash headless scrapers before they even fetch content. What we see from Vercel with their isagentic is about improving your website for Machine Accessibility. Agents don't care about the design of your landing page. They just want to extract its content. Want to know what to do? -> building deterministic APIs, agent-first auth, and machine-readable data pipelines. I would call it instead Agent Interoperability, but yeah I guess you can't brand it as "AI"

• 
  LilRhodySpecial (@rhody_special) reported 4 minutes ago

  @eastdakota I cancelled Spotify because they partnered with Cloudflare. Bad move stepping on artists. Folks do your selves a favor do not use any voice models cloudflare and the rest of the Stanford scam artists are working hard to make sure you own nothing and that includes your voice

• 
  Nick Blow (@NickBlow) reported 8 minutes ago

  @hackerdocc Vercel’s main value prop was making AWS easier to use but with agents they kinda solve that problem already, trivial to do some iac stuff. Fluid compute is genuinely pretty cool and not many companies compete - though vercel is still v v expensive even with the efficiency there. Cloudflare skirts the issue by charging for CPU vs wall clock. Cloud run and lambda managed instances are *sort* of analogous but not quite.

• 
  Welldone (@welldone_tech) reported 10 minutes ago

  Cloudflare shipped WriteGuard for MCP servers: agents can read data, write operations need an explicit gate. Unrestricted tool access is the actual production risk with agents - not that the model is wrong, but that a prompt injection or a hallucination reaches a database that never should have been writable in the first place. Read/write separation for agents isn't a Cloudflare feature. It's the same principle behind every gate we put in our own process - a senior approves the spec before code exists, a different model reviews it, an engineer deploys manually. The tool doesn't get more trust than the person watching it.

• 
  aginaut (@aginaut) reported 12 minutes ago

  AWS AgentCore Payments: The Rails Are Opening. The Junction Is Not Settled. On 18 August, AWS made an odd move for a platform widening its role in agent payments: it declined to choose a payment rail. AgentCore Payments moved from preview to general availability with MPP beside x402 and, according to AWS, one developer integration across both. AWS imposes no extra charge for its Payments APIs. Wallet providers still charge; Gateway, Policy and CloudWatch still meter usage. If AWS were competing primarily for the rail, supporting two rivals without an API fee would be a peculiar opening move. The mismatch deepens at the other side of the transaction: AWS WAF can already challenge an AI agent for an x402 payment through Coinbase before admitting it to content. MPP and Stripe support were still described as forthcoming. For an allocator, protocol adoption is therefore the wrong scoreboard. If the rail is becoming plural and inexpensive to integrate through AWS, which part of the transaction is AWS trying to make indispensable? The missing fee makes the bundle the live hypothesis AWS is not alone in making payment rails interchangeable. Cloudflare supports x402 and MPP. Visa and Mastercard are building protocol-agnostic or multi-rail agent-payment capabilities. The Linux Foundation’s x402 Foundation brings cloud, payment and technology companies into the same standards effort. This demonstrates protocol plurality and standards activity—not adoption or power. That may shift the source of scarcity. As payment syntax becomes easier to support, a potentially scarcer task is coordinating the records around it: identity, authority, counterparty, budget, policy, execution and evidence. AgentCore already places several of those functions near one another. Payments now sits beside identity, Gateway discovery, bounded sessions, Policy pathways and observability. WAF separately approaches seller admission. These are not one integrated marketplace, and AWS does not control the entire transaction. They do, however, give AWS an early option on the environment in which agentic economic action is governed. The Platform Envelopment hypothesis Thomas Eisenmann, Geoffrey Parker and Marshall Van Alstyne call this platform envelopment: a platform enters an adjacent market by bundling a new function that shares users and technical components with its existing services. The bundle changes the contest. A standalone payment service must now compete with payments embedded where agents are identified, authorised, routed and observed. That is the strategic possibility in AgentCore: protocol-agnostic support could let AWS coordinate several payment systems inside one governed environment while making its surrounding services more useful together. Yet bundling alone is not platform power. If users can bypass AgentCore, carry identity and evidence elsewhere, or multi-home without friction, this is integration—not durable envelopment. Follow the right, not just the payment An autonomous transaction rarely specifies every relevant contingency in advance. It still needs answers to ordinary institutional questions: Who approved the spend? Was the recipient valid? What was delivered? Which record proves it? Who can revoke authority or remedy failure? This is why payment begins to cluster with identity, policy, audit, reputation and recourse. The payment message moves value. The surrounding records make the action acceptable to the next institution. One diagnostic keeps the layers separate: RAIL → JUNCTION → RIGHT Rail: What became interchangeable? Junction: Which operating records must still be reconciled? Right: Whose record will the next institution accept? Today, those rights remain divided. The enterprise principal funds, mandates and revokes. Application code must validate the recipient. AgentCore can constrain amount and time, route through supported protocols and preserve operational evidence. Wallet providers sign. Merchants price and deliver. Financial networks and payment providers retain settlement, fraud and dispute functions. A payment proof therefore establishes neither satisfactory delivery nor a universal right to refund or remedy. Portable-record systems form a counter-architecture. AP2 under FIDO stewardship and W3C Verifiable Credentials target portable mandates or identity evidence. On Ethereum, draft ERC-8004 and ERC-8183—with Virtuals ACP implementing the latter direction—target identity, reputation, validation and escrow. This is documented standards and implementation activity, not evidence of broad adoption or transferred power. Open rails cut both ways Modularity is the counterforce to envelopment. Open interfaces can commoditise the rails beneath AWS, increasing the value of AgentCore. They can also commoditise AgentCore if customers can move their identities, mandates, policies, wallets, reputation and audit history intact. The practical test is not whether an interface is called open. It is whether substitution works: Can an enterprise multi-home cheaply? Can another cloud or network recognise the same mandate? Who controls schema changes, revocation and the evidence required after failure? Until those answers settle, AWS holds a candidate position—not the junction itself. Three futures from the same move The current evidence supports an option space rather than one forecast. 1. Managed-junction consolidation. If AgentCore Payments drives attachment to AWS identity, policy, discovery and observability—and operating state becomes expensive to move—value could concentrate around managed control planes and their security, compliance and monitoring complements. 2. Federated recognition. If portable mandates, credentials, reputation and escrow records gain acceptance across clouds, wallets and marketplaces, value could move towards cross-platform identity, verification, translation and assurance rather than one platform owner. 3. Institutional retention. If enterprise procurement and treasury continue to hold spending authority while Visa, Mastercard, Stripe and other financial actors retain acceptance, fraud, settlement and remedy, cloud payments would remain useful orchestration while the authoritative economic record stayed with enterprise and financial institutions. These futures can coexist. Low-value machine purchases may favour managed automation, while consequential enterprise actions remain institutionally governed. The receipts that decide the path Watch four things: Attachment: Does Payments increase use or retention across AgentCore? Recognition: Which counterparties accept the session, policy and audit records produced or held around AgentCore? Portability: Can those records move across clouds, wallets, networks and marketplaces without material loss? Economics and remedy: Where do switching costs, adjacent revenue, disputes and paid-but-no-service outcomes accumulate? Protocol adoption alone is not enough to underwrite power. At minimum, Payments must produce attachment plus either non-portable operating state or measurable adjacent economics. The allocator’s question is not which payment protocol wins. It is whose record the next institution accepts, whether that record can leave—and which future becomes investable as those answers emerge. AWS has taken an option on power. Power has not yet transferred. Notes & conceptual credits: Platform Envelopment follows Eisenmann, Parker and Van Alstyne. The supporting logic draws on transaction-cost and incomplete-contract research associated with Coase, Williamson and the Grossman–Hart–Moore tradition; the countercase draws on Baldwin and Clark’s modularity work and Ghazawneh and Henfridsson’s boundary-resource research. RAIL → JUNCTION → RIGHT and its application here are Aginaut syntheses. Product and standards claims remain bounded by the first-party materials available on 22 August 2026.

• 
  Adel Bucetta (@adelbucetta) reported 14 minutes ago

  @opencode @Cloudflare error rates are just a symptom of deeper issues, usually around architecture or funding

• 
  The TAO Daily (@taodaily_io) reported 15 minutes ago

  The internet is becoming easier to restrict. Cloudflare is moving to block AI crawlers by default. Governments are increasingly shutting down national internet access. So who controls what you can reach? UR (SN25) is taking a different approach. It brings 80,000 residential IP providers across 100 countries and 350,000 users into Bittensor. We covered UR’s two-tier miner economy, token mechanics, and settlement system:

• 
  scott (@scottonote) reported 15 minutes ago

  @NateMeyvis correct primitives can help mitigate this. MVC for "classic" web request/response, cloudflare Durable Objects for actor pattern, polars over pandas. something something map reduce

• 
  Felix (@Reezxy23) reported 19 minutes ago

  There has never been a cheaper time to build. Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel= deploying. (Free) Namecheap = domain.
($12/yr) Stripe = payments. (2.9%/
transaction) GitHub = version control.
(Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking.
(Free) Upstash - Redis. (Free) Pinecone = vector DB.
(Free) Total monthly cost to run a startup: ~$20

• 
  Aymane (@aymanemsi) reported 20 minutes ago

  @blendimehmeti3 @opencode @Cloudflare Damn 3$ is not that much at all lol

• 
  james (@f82james) reported 20 minutes ago

  @opencode @Cloudflare nah bruh **** still doesnt work

• 
  Michael Flux (@michaelflux) reported 22 minutes ago

  I don’t use Sentry. I don’t use PostHog. I don’t use any dedicated error-monitoring SaaS. Every single error in my stack - backend, frontend, queues, Durable Objects, etc, lands in Cloudflare Observability the moment it happens. Then a tiny custom toolbar app pings my account every 15 minutes, surfaces any new errors, and I fix them typically within a few hours. Over time the apps just… stop breaking. Here’s the exact system (and why Cloudflare is pretty cool);

• 
  Cody Viveiros (@The_Cojovi) reported 23 minutes ago

  Cloudflare just shipped a browser with no Chromium. Kitesurf runs agents, not humans — V8 isolates, 3-7x less CPU/memory, no tabs or 60fps. The web was never built for machines. We just started pretending it was.

• 
  Diego (@diego_smez) reported 23 minutes ago

  Spent a while debugging why dopost wasn't working for some users in Spain. The issue? Football. LaLiga is blocking shared Cloudflare IPs to fight piracy, taking legitimate services down with them. Somehow Javier Tebas ended up in our incident log.

• 
  Sumedh Bengale (@ssbengale) reported 23 minutes ago

  @omkarships Cloudflare, as I change the Nameservera on other providers to cloudflare either way. They are the cheapest one, without the vendor lock in discounts. Too bad that they don't support a lot of TLDs