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:

• 
  Srishti (@srishticodes) reported 2 minutes ago

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

• 
  PANKRATION (@WEB3Seer) reported 2 minutes ago

  22/ Cloudflare Waitlist launched for Monetization Gateway. New product for charging for resources with settlements in stablecoins via x402 protocol. #Cloudflare 23/ AscendEX Has not posted on X for 9 days. Withdrawals not processed → deposits accepted. Reports of withdrawal issues without response. Delays/non-processing of user withdrawals while continuing to accept deposits. #AscendEX

• 
  Omni G (@OmniG7) reported 2 minutes ago

  @vxunderground @Cloudflare @Cloudflare wtf bro quit ******* up research, let smelly get zee malvares!

• 
  Javi (@rameerez) reported 3 minutes ago

  @codeandfish I think Amazon SES is the best provider there is for sending emails. If you stick to SES only, AWS is not too complex: just create credentials and verify your domain. I don’t remember the numbers off the top of my head but I think it’s significantly cheaper than Cloudflare too. I’ve never paid more than pocket change for SES, even when sending many many emails a day. I would recommend staying with it if you’re already using it - you’re probably not going to get any added value from changing providers. That being said, go ahead and try it for yourself! Maybe I’m wrong and you can prove me wrong and everyone benefits from that!

• 
  Viswa Reddy (@lviswanath) reported 3 minutes ago

  So I made the pragmatic call: Moving the main customer-facing application to Vercel + Cloudflare. Not because self-hosting is wrong — but because for this workload right now, the velocity gain is massive. GitHub-native CI/CD that just works, instant previews, edge performance, and zero time fighting tunnels or rate limits during deploys. My brain stays on the actual product.

• 
  0xLoopTheory (@0xLoopTheory) reported 9 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.

• 
  Akintola Steve (@Akintola_steve) reported 10 minutes ago

  Q: What is a CDN? CDN = Content Delivery Network. Instead of downloading files from Nigeria to the US every time… Copies are stored globally. Users download from the nearest server. Benefits: • Lower latency • Faster websites • Reduced origin server load Popular CDNs: • Cloudflare • Akamai • Amazon CloudFront

• 
  João Tomé (@emot) reported 20 minutes ago

  I was curious whether the earthquake in Venezuela had any lasting Internet impact as well, and it looks like it did, with latency staying higher afterwards. Median latency increased by roughly 15-20%, from around 68 ms to about 80 ms. Latency variability also increased, with the 75th percentile rising from roughly 90 ms to 110-120 ms, suggesting a less stable network. (from Cloudflare Radar’s IQI).

• 
  Fire Watcher Watch (@FireWtcherWatch) reported 21 minutes ago

  @NeelMehta420 @khyimiq @DalitDetector One of the more recent major CloudFlare outages (February this year) was because they pushed a change which automatically deregistered 25% of BYOIP addresses. Total incompetence, and caused a multi-hour outage for many millions of people.

• 
  ProxyStats (@ProxyStats) reported 24 minutes ago

  @getpaidfirlive Not only you - its been down for everyone since June 28. We pulled the registry records to check the "seizure" rumors: routine registrar lock (not serverHold), Cloudflare nameservers untouched, domain paid through 2027. Looks like an outage, not a takedown.

• 
  Vedant Anand 🐲/acc (@Vedantsx) reported 25 minutes ago

  @samlambert Gotcha ser 🫡 Btw I'm unable to migrate from Supabase to Planetscale in Cloudflare Startup program, can you kindly help me somehow?

• 
  fren (@frenbot31488) reported 25 minutes ago

  @Itsuki_i_VRC @iris__vr he posted a long rambling explanation of why he can't take down ripping sites, cloudflare is a CDN/proxy, doesn't host the files, DMCA notices to them don't result in removal. he deleted it after like 2 days, 4 retweets, went from 18 to 16 likes, so two people actually read it

• 
  nimaUSD (@nimaUSD) reported 26 minutes ago

  For 30 years, the web ran on one deal. content for attention. AI agents just broke that deal, and Cloudflare thinks it has the fix. Their new Monetization Gateway lets any website, API, or dataset charge per request, with payments settling in stablecoins over Base. 119 million transactions already processed. Zero protocol fees. And it's just getting started. Here's what it means if you're building in the @Base ecosystem.

• 
  123 (@whatwouldgkdo) reported 26 minutes ago

  @Cloudflare U Guys got processing issues? tried to buy 3 domains all 3 with different cc and none worked. tried 3 debit cards none worked tried 2 different paypal accounts, none worked.

• 
  spaghetti.sol (@spagsol) reported 28 minutes ago

  Yes, Cloudflare had issues again