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:

• 
  swyx (@swyx) reported 2 minutes ago

  the #1 thing that is driving me to build my own vibecoding platform rn is that none of them - and i lov vercel, cloudflare, netlify etc - none of them really close the loop for you in terms of setting you on the right path with errors and pinging you when **** fails (**** always fails) there's way too much "webmaster" infra to setup for every single project and i just want to do it once and for all, instead i'm being asked to npx posthog wizard here and npx arize skills there and it all just needs to be swallowed up into One Thing.

• 
  Hungry Coder (@thehungertocode) reported 3 minutes ago

  @Cloudflare Trusting @Cloudflare edge network 🛜

• 
  Iso Ledger (@JamesDula82) reported 5 minutes ago

  What Is @t54ai Lets audit. AI agents are already moving money. Unverified. Unaccountable. Nobody held responsible when something goes wrong. That's the problem t54 Labs is solving. Founded January 2025. San Francisco. $5 million seed round closed February 25, 2026. Led by Anagram, PL Capital, and Franklin Templeton. Ripple came in as a strategic investor. Here's what they actually built. Four products. One mission. Know Your Agent — identity verification for AI agents. The same way KYC verifies humans, t54 verifies the agent itself. Who created it. What it's authorized to do. What its limits are. Real-time risk — flags suspicious activity before funds move. Not after. Before. Credit — credit lines for AI agents based on verified identity, risk scores, and transaction history. An AI agent with a credit score. That's the world we're entering. x402 Facilitator on XRPL — this is the direct XRP connection. t54 built an open-source trust layer on top of Coinbase's x402 protocol and deployed it on the XRP Ledger. Their XRPL x402 Facilitator lets AI agents pay for services using XRP and RLUSD directly. Agent calls an endpoint. Payment request arrives in the HTTP header. Agent pays in XRP or RLUSD. Settlement in seconds. No bank account. No API key. No human in the loop. How XRP is connected — the honest answer: The x402 Facilitator uses XRP and RLUSD as the payment assets. When an AI agent pays for a service through t54's infrastructure on XRPL, XRP is one of the settlement options. Every transaction on XRPL burns a small amount of XRP in fees regardless of which asset settles. The honest flag — at current volumes this is not significant XRP demand. The thesis is about scale. 42% of US consumers in a YouGov study said they'd allow an AI agent to make purchases for them if it guaranteed the lowest price. If that materializes at institutional scale the transaction volume on XRPL becomes meaningful. The institutional stack around t54: Evernorth — Ripple-backed digital asset treasury targeting $1 billion+ in institutional XRP holdings — already integrated t54's infrastructure for autonomous treasury operations on XRPL. ✅ Franklin Templeton's SVP of Digital Asset Management called t54 "the trust and verification framework institutional finance will require as AI agents become market participants." ✅ Markus Infanger of RippleX said autonomous systems are becoming economic actors not just tools — and the financial infrastructure needs to catch up. ✅ Today Mastercard named t54 as a launch partner for Agent Pay for Machines alongside Ripple, Coinbase, Stripe and Cloudflare. ✅ The sequence: Coinbase builds x402 in May 2025. t54 builds the trust layer on top of x402 on XRPL. Ripple and Franklin Templeton fund it. Evernorth integrates it. Mastercard puts it in a global press release alongside their entire partner ecosystem. The internet forgot HTTP 402 for 26 years. AI remembered why it was needed. t54 is the identity layer. XRPL is the settlement layer. XRP and RLUSD are the payment assets. The machine economy needed a trust layer before it could have a payment layer. Now it has both. We audit the plumbing 🛡

• 
  Ivon Huang (@Ivon852) reported 6 minutes ago

  Finally made the switch. Actually, when you buy a domain, you can transfer it to another registrar. This is called a domain transfer. If you feel your current domain registrar is ripping you off, you should jump ship as soon as possible. If you don’t need an all-in-one website-building service, buying a domain from GoDaddy seems very uneconomical. They are just very good at advertising in many countries. Domains from Porkbun and Cloudflare Registrar are much cheaper. My website is built with a JAMstack setup using Hugo SSG and ***. And yet, I renewed my domain for four years, paying around $20 per year for a common .com domain. I honestly can’t believe I stayed on GoDaddy and kept feeding the money machine, even though I wasn’t using their WordPress services at all.

• 
  Miguel Cardoso (@ODordio) reported 8 minutes ago

  After a both brief and long 5 months I was part of the recent culling at Cloudflare. But clankers can't stop clanking thus proud to say that I am joining Snyk to work on Snyk's pentesting clanker and help push it to GA. No vulnerability is gonna be safe from me and my robots.

• 
  Gennaro (@fourweekmba) reported 8 minutes ago

  Mastercard just launched Agent Pay for Machines. AI agents can now buy things autonomously. micropayments down to fractions of a cent. machine-to-machine. always on. 31 partners: Coinbase, Stripe, Adyen, Cloudflare. settlement: cards + stablecoins via Polygon, Solana, Base. Apple gave agents eyes and hands. Mastercard just gave them a wallet.

• 
  Triode (@Triode_in_situ) reported 9 minutes ago

  I can’t help but think any glitch I encounter on web UIs most recently Cloudflare is due to AI Slop code.

• 
  Velvex Vancreed (@VelvexVancreed) reported 11 minutes ago

  @Damagehands @AyakaMods exactly it goes to cloudflare and which they don't like the content so they will deny access to their service.

• 
  chan (@chantastic) reported 17 minutes ago

  @jeflopo I'm annoyed because the frontend of these sites has to do SO little. all the serious work is Cloudflare Workers, Queues, AI Gateway, and Durable Objects. so it's just an annoying speed bump to have UI framework issues

• 
  Jay.TL (@JayTL00) reported 19 minutes ago

  Both Visa and Mastercard launched agent payment rails this week. Zero real transactions have cleared through either. Visa Intelligent Commerce gives AI agents tokenized card credentials — your agent gets its own identity on a network processing 300 billion transactions a year. Mastercard's Agent Pay for Machines (AP4M) went further: agents paying other agents, machine-to-machine, no human in the loop. 30+ partners including Stripe, Coinbase, Solana, Polygon, Aave, Cloudflare, Ripple. The optics are undeniable. Two payment networks that move $30 trillion+ annually are building for a world where the buyer isn't human. But the substance is mostly slide deck. Three things the press releases don't mention: 1. Zero production volume. No transaction counts, no throughput benchmarks, no live merchant integrations with actual agent checkout flows. The 30+ AP4M partners are logos on a launch graphic. Every "early adopter" is testing in sandbox. Visa's own CFO Chris Suh said plainly: agentic commerce and stablecoins "won't pay off in the next six months, but could over the next six years." That's not a launch. That's a forward-looking statement with a PR budget. 2. The authority problem has no answer. Payment rails move money. They don't decide who's allowed to move it, when, or how much. When your agent spends $2,000 on cloud compute from another agent, who set that limit? Who audits it? Who's liable when the agent hallucinates a purchase? Visa's model (human-delegated tokens with spending caps) at least has a governance story. Mastercard's machine-to-machine model has a governance vacuum. The "fraud detection" and "spending limits" mentioned in press releases are features that don't exist in production yet. They're on the roadmap — which is where most agent infrastructure lives in 2026. 3. Five competing agent payment protocols launched in 2026. ACP. x402. MPP. AP2. AP4M. Each with different trust models, settlement layers, and identity frameworks. The fragmented landscape is a feature for early experimentation and a disaster for adoption. Merchants won't integrate five agent payment protocols. Agents won't carry five wallets. The consolidation hasn't started because nobody has enough transaction volume to matter. The real signal isn't the technology. It's that the two largest payment networks on Earth decided in the same week that agent commerce is real enough to allocate engineering resources, partner integration teams, and public marketing budgets. They're not building because agents are buying things today. They're building because if agents ever do buy things at scale, whoever owns the rail owns a tax on autonomous commerce. The bet is simple: the marginal cost of building agent payment infrastructure in 2026 is tiny compared to the cost of being locked out of a new transaction layer in 2028. Whether that bet pays off depends on a question none of these announcements address: what happens when the first agent makes a $50,000 mistake at machine speed on a rail designed for that speed? That's not a technology problem. It's a liability problem. And nobody has underwritten that policy yet.

• 
  Noisey Kid 🇬🇧 (@noiseykid) reported 19 minutes ago

  @RealSteveVaughn @jimstewartson Blocking is the frontier, and will reduce the quality source further. Cloudflare network data shows that 57.4% of all web requests are now initiated by automated bots and AI agents. More bots than humans. I only need to look at my own site data to see the very obvious explosion

• 
  Jason from BallotScore.com (@goldenelephant1) reported 23 minutes ago

  @Cloudflare What i see is hackers using Cloudflare to circumvent their services by using them as a reverse proxy. I have seen multiple attacks trying to grab my .env, checking for wp-install etc files all from Cloudflare IP's. Reported it to You. You said **** off!

• 
  inder (@InderpreetSingh) reported 29 minutes ago

  Looks like @Cloudflare dashboard is down, but just saw "Organizations Beta". I hope thats the case. All my projects are co-mingled in a single account right now.

• 
  Tushar Dwivedi (@tush_2708) reported 30 minutes ago

  @kritikakodes For 50 users, get an adult "chhotu" to do the job that the system is supposed to do. A chhotu to run and call the cab. A chhotu to run and take documents to your CA, download and email, download and print, scan and email, whatever be the pain point. For 50 users, you need a validated business model, not a software system. My milkman caters to more users than this. If interviewers ask stupid questions, they should expect stupid answers. For 50 users, you can choose the worst design decisions intentionally and can still justify them. 1. Database Schema: "I will store all the data in an xlsx file, and will reread the file every time an API request comes. I will use another .lock file to control access when writing new data to this file" But what about "linearly degrading performance?" "What degradation? My API will still respond within 200 ms to all your 50 users" 2. Cloud deployment strategy: "What cloud deployment? I will run this system on a Raspberry Pi connected to a hard disk, with a cron job to do backups on 2 other hard disks connected to another Raspberry Pi. And I will set up Cloudflare tunnel to it, for your 50 users" 3. Disaster control? "I will use this 2000 rupee router power backup device"

• 
  Frosky703 (@Frosky703) reported 32 minutes ago

  Three devices, three different Cloudflare WARP modes. Same tool, different reasoning for each. Servers use DNS over HTTPS only. The ARM STB runs oracle feeders that pull price data from Binance. Some ISPs in Indonesia throttle or block crypto exchange traffic. Encrypted DNS resolves that without routing all traffic through Cloudflare. Laptop uses full WARP, but only on public WiFi. Campus networks, coffee shops, anywhere the network itself is not trusted. On stable home network, WARP is off. Phone uses WARP selectively when accessing Binance. Same reasoning as the STB, consistent access without depending on ISP behavior. Not a blanket policy. Each device has a specific reason. That's how security configs should work. Not maximum protection everywhere, but the right protection for each context and threat model. @Cloudflare #Networking #Security #BuildInPublic