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:

• 
  SYL Vexora- Jaron K Bragg (@JaronBragg) reported 4 minutes ago

  @its_sidraa Why not skip namecheap and just use cloudflare for both domain and DNS? Cloudflare actually puts my website on the map. Namecheap I never seen it and was hard for others to surface. Other than that it makes sense.

• 
  Samuel 🦤 (🧱,🔥) (@samuellhuber) reported 5 minutes ago

  @GeoffreyHuntley @Cloudflare Isn’t BGP fundamentally broken? At ETH Zurich they developed the Scion Internet architecture because of it

• 
  Zinoun Badr-Eddine 🇲🇦 (@xoniques) reported 7 minutes ago

  @aiob_me @irachdaoui You need at least 5$ worker to get mail service ! But yes ! Cloudflare is dope even ai worker model have a free tier

• 
  Nuotrix (@Nuotrix) reported 8 minutes ago

  @world_xyz @worldnetwork @Cloudflare if this is actually them that's so cringe wtf

• 
  Kaifyyy.sh (@Iamkaifyyy) reported 11 minutes ago

  - 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 There has never been a cheaper time to build. Helps me a lot I’m gonna bookmark it

• 
  Jblahs320 (@jblahs320) reported 17 minutes ago

  @philthatremains What happened to parenting. My child doesn't have access to this stuff because I monitor and take active steps to block her. Not only do I run heavy network wide ad blocking but also use Cloudflare DNS families. To completely block adult content. On top of that no Social Media.

• 
  Spook ✮⋆˙zinemaxxing (@sp00ky11_) reported 21 minutes ago

  Website is finally working after one million cloudflare issues

• 
  Anakin (@anakinHQ) reported 21 minutes ago

  On June 2, Cloudflare blocked every AI agent. Except 19. Playwright-based pipelines went down fast. Health monitoring tools that track drug pricing and patient data feeds, serving millions of people, stopped pulling data overnight. Wire does not use a browser. Nothing for Cloudflare to challenge. It kept running. Explore Anakin's Wire catalog, now with over 4700 actions!

• 
  Matt Katz (@0xkatz) reported 21 minutes ago

  Extremely bullish for x402. I always thought x402 was the best solution, yet feared that adoption may be slowed by integration hassle, compared to (for eg) agent cards. But if everyone using cloudflare (to a first approximation ~= all apps) is able to support x402, this is no longer an issue

• 
  Lilith Datura (@LilithDatura) reported 23 minutes ago

  @thePM_001 @Cloudflare nano-payments, damn I'm behind.

• 
  Mersh (@GooningOnTumblr) reported 24 minutes ago

  @Philo01 @Cloudflare In case you’re poor and your auto renewal doesn’t go through

• 
  Ranjith | Building PrivacyDrift.com (@MakeDesignPop) reported 25 minutes ago

  Day 3 of @PrivacyDrift_ - Tiring day. Struggled with a bug for hours and still couldn't fix it. Thanks to Cloudflare... I guess. - Wrote a script and designed the UI screens for the launch video. - Fixed some SEO issues and made improvements to the website. - Didn't send any new emails today 🫠

• 
  Exci (@ai_exci) reported 26 minutes ago

  @ZubairIbnZamir @Cloudflare @CloudflareDev Down again today. 7 hours now.

• 
  0xLoopTheory (@0xLoopTheory) reported 30 minutes ago

  Google is moving a number of its TLS certificates from RSA to ECDSA. Not because ECDSA is quantum-safe. It is not. Not because RSA is about to fall. It is not. Not because someone at Google forgot Shor's algorithm exists. They did not. The announcement is easy to misread. Google Trust Services says that during Q2 2026, a number of Google services that have historically provided an RSA leaf certificate will shift to an ECDSA leaf certificate by default. So in the middle of the post-quantum migration, Google moves certificates from one Shor-vulnerable algorithm to another. Under standard resource estimates (Roetteler et al., 2017), breaking P-256 requires fewer logical qubits than breaking RSA-2048. On paper, this is a step toward the more quantum-fragile primitive. It still makes sense, and the reason is the most useful mental model I know for the PQ transition: TLS does not migrate as one block. It migrates in layers, and each layer faces a different threat on a different clock. Key exchange is on the fast clock. Recorded traffic can be decrypted retroactively: harvest now, decrypt later. So it moved first. X25519MLKEM768 is now default or automatically advertised in current major browser stacks: Chrome, Edge, Firefox, and Safari on Apple's 26-generation OS releases. By late October 2025, the majority of human-initiated traffic with Cloudflare was already using post-quantum encryption. Certificates are on the slow clock. For live TLS authentication, a signature must be unforgeable at the moment it is verified, not forever. A quantum computer in 2035 cannot retroactively forge the certificate that authenticated your session today. And the slow clock is forced by a budget nobody can print more of: bytes. An ML-DSA-44 signature is 2,420 bytes. A raw ECDSA P-256 signature is 64 bytes. Cloudflare estimates a drop-in swap would more than double the bytes most QUIC connections transmit over their lifetime. Chrome says plainly it has no immediate plan to add traditional X.509 post-quantum certificates to its root store. Chrome's public-WebPKI plan is Merkle Tree Certificates, now being developed in the IETF PLANTS working group, against Google's broader stated 2029 PQC migration timeline. So the ECDSA move is classical housekeeping. Google's stated rationale is efficiency: smaller to transmit, cheaper to process. The announcement does not mention post-quantum once. Which layer is migrating? Against which threat? With which ecosystem attached? Ask those three questions and most "why not just deploy PQC now" takes dissolve. The honest counterweight: maybe the slow clock is not as slow as the WebPKI assumes. Roots live for decades. Devices outlive their update channels. Gidney's estimate for breaking RSA-2048 dropped from 20 million noisy qubits in 2019 to under one million in 2025. If you think certificate authentication has less time than the ecosystem assumes, that is the argument worth having. I would like to hear it.

• 
  Jordan (@jstamby) reported 33 minutes ago

  Rebuilt a plumber's website last week. The old site scored 31/100 on a technical SEO audit. The new one scored 94. What changed: → 6 pages became 69 (every service × every city he covers) → Correct schema on every page (the old one literally geolocated him to the wrong state) → JSON-LD that makes each page citable by AI engines the day it deploys → Astro static + Cloudflare Pages, push-to-main to ship Six AI agents built it in parallel — one researched keywords, one designed, one wrote, one validated schema, one reviewed, one ran the launch gate. I didn't write 69 pages. I orchestrated the swarm that did. So glad I left Wordpress behind in 2025. Now I'm 10,000% more productive as a solopreneur.