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:

• 
  Uche | Tech Solution Expert (@Nueltek) reported 2 minutes ago

  @jayhemz Cloudflare to the rescue for a single point of failure? How exactly is Cloudflare supposed to handle that? I thought Cloudflare mainly helps with bandwidth, caching, and DDoS protection. How does it handle a VPS crash, server hardware failure, PostgreSQL corruption, or even a misconfigured firewall? Also, the problem usually isn't bandwidth. The real bottlenecks are CPU, RAM, disk I/O, database connections, etc. A VPS can run out of RAM long before it comes close to using 10TB of bandwidth. Anyways, for small brochure websites, I agree the tradeoff is usually worth it. But for SaaS products and other critical systems, I'd still want more isolation and redundancy, to be honest.

• 
  Abdulmajeed (@0xabma) reported 4 minutes ago

  Unpopular opinion: next.js is practically malware if you try to deploy it outside of vercel. ​spent hours fixing broken static exports, figuring out my proxy config won't even run on @Cloudflare unless it's renamed to a middleware file ​the vendor lock in is getting ridiculous.

• 
  kai🏳️‍⚧️ (@kai_blud) reported 7 minutes ago

  damn you cloudflare how dare you not magically know my ip address definitely not my fault for forgetting shi grrrrr frick you cloudflare

• 
  Basemail (@Basemail_ai) reported 7 minutes ago

  x402 (Coinbase/Cloudflare) + AP2 (Google/Coinbase) = payment protocols built for agents — HTTP 402 Payment Required finally activated after 30 years dormant in the spec — agent requests resource, server returns 402, agent pays in USDC, access granted, auditable end-to-end reality check: CoinDesk March 2026 — x402 processes ~$28K daily volume, 131K transactions, $0.20 average, Artemis analyst "the x402 agent payments boom is still mostly a mirage" — half of observed transactions are self-dealing or wash trading — $7B ecosystem valuation, $28K daily real volume but the protocol design reveals a deeper gap — x402 handles the PAYMENT moment (request → 402 → pay → access) — AP2 handles the COMMERCE layer (negotiate → pay → receipt) — neither handles what happens AFTER payment: purchase confirmations service credentials delivered via email account creation receipts API key provisioning notifications dispute resolution communication ongoing service status updates an agent pays for an API subscription through x402 — where does the welcome email go? agent buys cloud compute through AP2 — where do the login credentials arrive? agent purchases a domain — where does the registrar send verification? payment stack: x402 + AP2 + USDC on Base $0.0001 per transfer ✅ identity stack: ERC-8004 340K wallets 8.7M attestations ✅ communication stack: ❌ agents can pay but can't receive what comes after payment #AIAgents #x402 #Web3

• 
  TaTa ◕_◕ (@hbarTaTa) reported 7 minutes ago

  Cloudflare sees a future measured in millions of TPS. @Cloudflare CEO @eastdakota says AI agents could generate between 5 million and 50 million monetizable TPS across Cloudflare's network alone. According to Prince, the internet of AI agents will need infrastructure capable of 100 million TPS to support sustainable business models, and Cloudflare is actively looking for L1 infrastructure capable of handling it. "The transaction volumes are going to be extraordinary." Source: @Bankless

• 
  z1xus (@z1xus) reported 9 minutes ago

  recently tried deploying to aws' ec2 for the first time, after years of using different vps providers. it really isn't that bad, i'd say their dashboard is even easier than cloudflare. no idea why it has this reputation in the community, maybe it used to be worse...

• 
  Matth4313 (@Matth4313) reported 19 minutes ago

  @KSimback Kevin, @MPP32_dev directly solves the “alternatives to frontier usage for the 90%” problem (and helps cut bills in the process). They built a universal payment proxy (think Cloudflare + Stripe for machine-to-machine) that lets any HTTP API accept instant, per-request payments from autonomous AI agents — no accounts, no API keys, no expirations, no human approval. • Agents discover + call services across protocols (x402, Tempo, etc.) and settle in USDC on-chain seamlessly • API providers (including cheaper/open-source inference, data, tools) get paid 100% instantly with zero platform cuts • One integration = agents can route to the right model/provider for each task without friction This is the missing payments layer that makes token-cost optimizing actually work at scale. The 90% of tasks move to optimized/cheaper endpoints because agents can pay for them autonomously and reliably. No more being locked into frontier subscriptions. Already live with their own Solana intel API and 4000+ MCP server users. Perfect infrastructure for the agent economy you’re tracking.

• 
  Durgesh Rathod (@DurgeshRathod3) reported 20 minutes ago

  Google Project Zero researcher Tavis Ormandy discovered the issue and immediately reported it to Cloudflare.

• 
  Elias Al (@iam_elias1) reported 22 minutes ago

  The neighbor's final advice was the most actionable. He sat down and wrote out a list of 6 things every internet customer should do: 1. Turn off the public Xfinity hotspot (or your ISP's equivalent Spectrum, Optimum, and Cox all do this too) 2. Manually set your Wi-Fi channel instead of "Auto" 3. Disable QoS / Smart Network "optimization" features 4. Change your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) 5. Buy your own modem and router, stop renting from the ISP 6. Test your speed with fast. com or speedtest. net using a non-ISP server, never trust your ISP's own speed test Total cost: $150-300 in equipment, paid back within a year. Total time: One afternoon of setup. Total impact: Often 2-5x improvement in real-world speeds. The customer went from paying $90/month for "fast" internet that crawled to paying $60/month for the same internet that finally worked.

• 
  Dav (@davafons_dev) reported 24 minutes ago

  @varunkrish @Hetzner_Online I'm using Cloudflare for CDN which works great, but I needed a VPS for my backend. In any case if their customer support is like this I worry about their SLAs... so might have to just try other proviers even if they are more expensive.

• 
  brokiem (@brokiemydug) reported 25 minutes ago

  @EsfandTV It's usually the ISP either have bad routing or throttling your bandwidth because they detect certain services to be bandwidth heavy. Might want to use a VPN like cloudflare warp

• 
  Jami (@expertwith_AI) reported 26 minutes ago

  The neighbor's final advice was the most actionable. He sat down and wrote out a list of 6 things every internet customer should do: 1. Turn off the public Xfinity hotspot (or your ISP's equivalent Spectrum, Optimum, and Cox all do this too) 2. Manually set your Wi-Fi channel instead of "Auto" 3. Disable QoS / Smart Network "optimization" features 4. Change your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) 5. Buy your own modem and router, stop renting from the ISP 6. Test your speed with fast. com or speedtest. net using a non-ISP server, never trust your ISP's own speed test Total cost: $150-300 in equipment, paid back within a year. Total time: One afternoon of setup. Total impact: Often 2-5x improvement in real-world speeds. The customer went from paying $90/month for "fast" internet that crawled to paying $60/month for the same internet that finally worked.

• 
  Michał Piszczek (@cdiamond) reported 26 minutes ago

  @GergelyOrosz Cloudflare treats the RCA like product documentation. most companies treat it like legal exposure

• 
  Justin Lahullier (@JLahullier) reported 31 minutes ago

  For years, software security was limited by how quickly we could find vulnerabilities. Now, it is limited by how quickly we can verify and patch them. Anthropic's unreleased model found 10,000+ critical flaws in a month across major systems, with a 90% validity rate. Cloudflare alone found 2,000. When AI discovery runs at machine speed, but your remediation cycle is still measured in weeks, the bottleneck is no longer security. It is operations. If you don't automate verification and patch deployment, AI discovery will simply bury your teams in a backlog they can never clear.

• 
  +EV Dingers (@EV_Dingers) reported 34 minutes ago

  @bet365help @bet365_us sorry but why would you need that info to fix a cloudflare problem It's still down but oh.bet365 and il.bet365 work fine