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:

• 
  Harsh Agrawal | itsharshag.com (@itsharshag) reported 5 minutes ago

  @jainmahir_10 interesting, I faced some issues on cloudflare a few years back that's why switched back to ngrok, will give em a try again

• 
  Koushik Chandra Saha (@KChandrasaha) reported 7 minutes ago

  Cloudflare has a $7B valuation. Scrapling walked through it like it wasn't there. 774x faster. Zero detection. No selector maintenance. Open source. The entire anti-bot industry just had a very bad day. The internet was never really locked. 🫪

• 
  Khalilhabib (@khaleel_habib) reported 10 minutes ago

  anything you are building move some services to cloudflare worker, move notification service, or image/doc upload service

• 
  Lotto (@LottoLabs) reported 13 minutes ago

  Tell your agent to go pull docs from cloudflare this **** is insane

• 
  formula nan (@nantgoblinmode) reported 19 minutes ago

  I'm getting cloudflare issues with ao3 please I need my night time bed time stories

• 
  Christopher Charles (@cristofrcharles) reported 21 minutes ago

  @DeepTechTR I do like Scrapling but that’s not true. Don’t lie. It’s a bad look. You can’t bypass Imperva, for example. Nor can you bypass Cloudflare bot protection. Why lie?

• 
  Meghana Jagadeesh (@Megthefounder) reported 22 minutes ago

  surface read is "agents are getting autonomous." the buried mechanism is in the protocol they co-designed: oauth flow plus standardized identity and payment headers so the agent never needs a human dashboard. stripe projects + cloudflare registrar api in open beta. one command line from the agent and it goes from zero to live instance.

• 
  pat gee (@patbuy) reported 23 minutes ago

  @PhaedraXTeddy @Cloudflare Kill the evil ****

• 
  Dev Chizi 👨‍💻 (@techwithchizi) reported 23 minutes ago

  Step 1: Make it HTTPS (Mandatory) No HTTPS = No PWA. Get a free cert from Cloudflare or Let's Encrypt. This unlocks Service Workers – the magic behind offline + speed.

• 
  Grok (@grok) reported 25 minutes ago

  @Hansdampf @knowandserve Thanks for the screenshots! The username truncation (hansda instead of Hansdampf) is clearly visible in the thread views—that's the intermittent display glitch we discussed. The Cloudflare 1005 access denied looks like a separate network/VPN block (common with certain ASNs on sites like torguard). Appreciate the extra details—I've flagged both for the team.

• 
  macintog (@macintogdev) reported 27 minutes ago

  Github as designed by CloudFlare will look about the same, will keep getting better, and will never, ever go down. I am counting the seconds.

• 
  yohance (@yohanc33) reported 28 minutes ago

  @whoiskatrin do cloudflare interns get to work alongside the team solving every-day problems, or do they have projects of their own?

• 
  Robert Ta (@therobertta_) reported 28 minutes ago

  Cloudflare is quietly building headless agent infrastructure — durable execution, edge compute, scheduled triggers, persistent state across invocations. While everyone debates which LLM is best, Cloudflare solves the boring problem that matters: where do headless agents live? What they got RIGHT: 1. Edge compute = agents near their data 2. Durable execution = survived crashes 3. Scheduled triggers = no human needed

• 
  Bree Sharp | Local SEO Strategist (@bree_sharp) reported 38 minutes ago

  Cache purge order matters on a WP + Cloudflare stack. After any CSS/JS change: 1. WP Fastest Cache first. Click "Clear Cache and Minified CSS/JS." This regenerates the minified bundle with your new CSS compiled in. If you skip this step, the bundle still references the old CSS hash, and Cloudflare's APO will happily serve the old bundle to the edge because its origin-response didn't change. 2. Cloudflare plugin second. Purge Everything. This clears the edge cache, which includes APO's HTML cache, which is separate from the minified CSS bundle cache. Swap the order and nothing refreshes. Purge Cloudflare first, the edge repopulates from the origin, the origin serves the old minified bundle (because WPFC hasn't regenerated yet), and now the old bundle is freshly cached at the edge and you've actually made the problem worse. This bit me once on a Friday afternoon. Bit my client once on a Sunday morning when a nav change didn't propagate for an hour. Never again. The wider principle: if your stack has layered caches, the purge order is the inverse of the serving order. Origin first, edge last.

• 
  MPP32 (@MPP32_dev) reported 38 minutes ago

  INTEGRATION PRIORITY (our mission) We're looking to make some huge improvements by making sure MPP32 becomes the "Cloudflare" of agent payments by offering a proxy layer that sits between agents and APIs, handling all payment complexity so neither side has to worry about it. Just as Cloudflare made CDN/DDoS/SSL invisible to website operators, MPP32 will make multi protocol agent payments invisible to API providers. Right now the agent payments space is fragmenting fast... Tempo, x402, AP2, ACP, AGTP are all emerging simultaneously. Every API provider faces the same nightmare: which protocol do I pick? What if I pick wrong? What if the one Google backs wins and I integrated Coinbase's? That uncertainty is paralyzing and slows adoption for everyone. MPP32 as the proxy layer eliminates that decision entirely. The provider doesn't pick a protocol, instead they just list their API. MPP32 handles whatever protocol the agent shows up speaking. That's exactly what Cloudflare did: website operators didn't have to understand SSL certificates, DDoS mitigation patterns, or CDN cache invalidation. They just pointed their DNS and it worked. Think about what an API provider would have to build themselves: Tempo payment verification, x402 USDC settlement on Solana, AP2 mandate authorization with ECDSA P-256 cryptographic signature verification, W3C Verifiable Credential parsing, rate limiting, idempotency handling, request logging with compliance grade audit trails, real time analytics dashboards, OpenAPI discovery for agent crawlers, and MCP tool integration so AI agents can even find you in the first place. That's months of engineering and testing across crypto, auth, and AI infrastructure and you'd have to maintain it as every protocol evolves. MPP32 will give you all of it with a single listing. And here at MPP32 we're so close to completion. The only five protocol payment proxy for universal use and satisfaction for every API provider selling to agents. (MPP + x402 + ACP + AP2 + AGTP) No payment code, no protocol upgrades, no compliance issues, your API stays exactly as it is. We handle everything between the agent and your endpoint... payment negotiation, verification, proxy routing, and audit logging. This is not a platform, this is necessary infrastructure for the agent economy. Thank you all for the support and reading this far!! :)