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:

• 
  orig (@the_real_ori) reported 3 minutes ago

  @sunglassesface @Cloudflare @PlanetScale Support is always the last unsolved piece, even at companies this good. Infra scales on its own, a Discord full of overworked humans does not. That gap (AI answers first, humans only on escalations) is the whole reason I am building in this space.

• 
  Ranjith | Building PrivacyDrift.com (@MakeDesignPop) reported 5 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 🫠

• 
  🐍Salazar.eth 🦇🔊 (@0xSalazar) reported 5 minutes ago

  Breaking news from yesterday - Robinhood L2 Chain went live on mainnet, built on Arbitrum - Robinhood partnered with Lighter for perps - dYdX rebrands to Arcus, DEX on Robinhood Chain - Drift rebrands to Velocity - World, Solana prediction market app, went live - Ethereum Institutional launched as an independent non-profit to drive institutional Ethereum adoption, anchor-funded by BitMine, SharpLink, and Joseph Lubin. - Ethena partnered with Robinhood, becoming the primary collateral asset issuer for Robinhood’s first crypto earn product via a Steakhouse-curated vault. - Cloudflare opened the waitlist for its Monetization Gateway, letting developers charge for web/API/MCP access with stablecoin settlement via x402. - Circle CEO Jeremy Allaire criticized OUSD, saying consortium stablecoins have a poor track record and that USDC handled 80% of all dollar stablecoin transactions in Q1. - Visa, Stripe, Mastercard, BlackRock, Coinbase and 140+ other firms launched Open USD (OUSD), a stablecoin that shares reserve revenue with partners - Forward Industries grew its Solana treasury to 7.55m SOL (~$576M) - DeFiLlama launched a MiCA exchange dashboard to help EU users compare licensed trading platforms by fees, liquidity, and KYC. - Aave Chan Initiative wound down operations following a governance rift with Aave Labs. - Pumpfun deprecated its Tokenized Agent launch option for new coins after community backlash over PVP dynamics. - Christoph Jentzsch proposed to dissolve the ENS DAO by burning the ENSv2 Universal Router key and distributing remaining funds, arguing the protocol’s goals are already accomplished

• 
  linda (@LindaOakland75) reported 6 minutes ago

  So Cloudflare is getting into stablecoin payments now? Wonder if this will actually take off or just be another waitlist that never opens.

• 
  tamimbuilds (@tamimbuilds) reported 7 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.

• 
  Ercan Ermiş (@flightlesstux) reported 7 minutes ago

  I'd like to personally thank CloudFlare because they fixed the session cookie issue on the login screen, and we can now continue using the same session without having to log in several times a day. It would also be great if we didn't have to say no to the cookie bar on the homepage every day. #CloudFlare

• 
  Adarsh Kumar Singh (@asin_adarsh) reported 7 minutes ago

  @sattyyouneed Cloudflare. At-cost pricing, no renewal games, no upsell wall. Moved everything there and never looked back.

• 
  🔥Phoenix (@GPhoenixForever) reported 12 minutes ago

  @LilithDatura Kind of like encryption with lava lamps at Cloudflare, noise vs signal down to the quantum fluctuations.

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

• 
  Fotten 🇳🇴 (@FottenSC) reported 16 minutes ago

  @SabinDeus Let me know if the load times are terrible in America. There is some cloudflare caching, but the backend is just running on a mini pc locally at my place in Norway.

• 
  Yousef Rol (@yousefrol) reported 16 minutes ago

  i need US hosted agent sanbox service THAT JUST WORKS. daytona, e2b, vercel, cloudflare did not give me what i want. "self host X" No. managed sanbox service.

• 
  Charu (@Charu_Sethi) reported 18 minutes ago

  Cloudflare just opened a waitlist to let any site on its network charge AI agents per API call, per dataset row, or per MCP tool call, settled in stablecoins. Monetization Gateway, announced 1 July, is built on x402 and names USDC and the new Open USD consortium stablecoin as settlement assets. It was built with the x402 Foundation, now under Linux Foundation governance with 25-plus members. The protocol itself is not new. What is new is that any site or API already sitting behind Cloudflare's edge, which is a lot of the internet, gets a one-step path to becoming a paid, machine-payable resource. x402's adoption bottleneck has not really been the protocol design. It has been integration friction for the long tail of API providers who would need to stand up their own facilitator relationship. This is aimed straight at that friction. Cloudflare has not disclosed what it charges for facilitating this, single-source, waitlist stage, worth being upfront about that. Does the edge network that already classifies and blocks bot traffic become the natural place to charge that same traffic instead? It would be a logical extension of what Cloudflare already does, but it is still a waitlist, not a shipped, priced product. Curious whether other CDN and edge providers follow, or whether this becomes a Cloudflare-specific wedge. @Cloudflare @coinbase @CoinbaseDev #x402 #AgenticPayments

• 
  mrow 🦦🦈 (@mrowmewo) reported 19 minutes ago

  @sugarsprink Before it was just the Cloudflare image and like 1minute loading times for every button you pressed for the tail end of June and EVEN WORSE for the start of July, this year it’s not even that bad…Dont even joke lad

• 
  jaykee (@jaykeelinkjuice) reported 20 minutes ago

  ★ Uploading data to the cloud is free. Downloading it costs $0.09 per GB. Cloudflare analysis shows 8,000% margins over cost. ★ Egress fees eat up 10-15% of total bills, yet most operators never check this line item separately. The 2026 reality. ◇ 68% of Google searches end without a click. When AI Overview appears, click-through rates drop 60%. ◇ 80% of search users rely on AI summaries. ◇ 42% of LLM users use AI for shopping recommendations. ◇ Publisher traffic is collapsing anywhere from 20% to 90%. ◇ 57% of web traffic is bots, not humans. ◇ Traffic coming from AI platforms is only 1% of the total.

• 
  Deepanker Verma (@deepanker70) reported 24 minutes ago

  Cloudflare is changing how AI crawlers can access websites. It will now block mixed-use crawlers by default. These are bots that both index sites for search and also collect data for AI training or AI agents. Now that a large part of it is bots used by AI companies, this decision matters. These mixed-use crawlers often use website content to answer user questions directly in chat tools. In many cases, users may never visit the original website. Cloudflare says website owners should have more control. It also says AI companies should clearly separate search, training, and agent use. If your content is used in AI answers, you should have control over it and possibly earn from it. For big publishers, this is a policy shift they can negotiate around. For small publishers, the impact can be much bigger. Small websites depend heavily on search traffic. If AI tools keep answering questions without sending users to the source, traffic can drop. That can directly affect ad revenue and the ability to keep publishing content. This change may help small publishers decide better. They can choose what AI companies can use and what they cannot. But there is also a risk. If they block too much, they may lose visibility in AI-based search systems. There is also a bigger question. Will AI companies follow these rules? #SEO #GEO #Cloudflare