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:

• 
  Anirudh Oppiliappan (@icyphox) reported 5 minutes ago

  @threepointone @AKuederle Not sure where all this anger is coming from. The folks on Bluesky (and me here) were poking fun at the banner text—which was apparently *meant* to be tongue in cheek! Wasn’t clear. Nobody’s trying to cancel Cloudflare. Let’s all chill out for a bit.

• 
  Mr Angry from Haight everything (@juvation) reported 5 minutes ago

  @SFFireCU logging in with the Cloudflare thing is broken "An error has occurred. Reference code: 600010"

• 
  Rahul Pramod Jaguste (@RahulJaguste) reported 5 minutes ago

  1/ Cloudflare just published why they are migrating to ML-DSA and not the compact post-quantum signatures. Their title: "Why we cannot wait for better signature algorithms." Correct call for the web. But a blockchain is a different problem, and the difference flips the answer.

• 
  Wizeman 🐂🀄 (@wizeman_AI) reported 7 minutes ago

  Noxa made $12M and disappeared, the trenches barely noticed Noxa was the biggest token launchpad on Robinhood Chain. In about a week they pulled an estimated $12M in fees. Then they just... shut down. July 11: Noxa said they’d stop accepting new token launches, right when CASHCAT was hitting peak volume 2 days later: Website went dark. Team blamed "Cloudflare issue" . July 14: Said domain would redirect to ENS and creator earnings could be withdrawn Late Tuesday: Posted they’d stop collecting fees entirely. 100% of revenue now goes to creators. Why they quit: They cited "concerns about low-quality tokens flooding the platform" Crypto Twitter was split: Half called it "based" for pushing back against spam. The other half called it a "generational fumble" and said they "killed the golden goose while making $3M a day" Meanwhile CASHCAT, the chain's breakout memecoin, dropped 33%+ in 24 hours. Even trader 0xAvast who rode it from $10k to $230M called it "irrelevant FUD"

• 
  Carqui 🐐 (@carquinyolis) reported 17 minutes ago

  @thecybersecguru @elhackernet In Spain whole cloudflare proxy IPs get banned with thousand of legitimate and corporate websites because just one seems to stream illegal sports. This is normal for non-technical government judicial powers..... Bad management

• 
  Hrishikesh Barua (@talonx) reported 17 minutes ago

  Outages today in both Google Cloud's and AWS's European datacenters (unrelated) caused many downstream services to blink out. We have been seeing this pattern of cascading service failures forever, but it only came under the spotlight after 2025's Cloudflare and AWS outages. The AWS outage in eu-central-1 was limited to a single AZ euc1-az2 in Germany, but it took out services like HENNGE One (a Japanese cloud security service), Confluent (managed Kafka), FusionAuth, among others. In addition, AWS Cloudfront suffered a global outage, leading to outages in downstream services like Frontegg, TigerData, Instructure (Canvas), Huggingface, Coda, Ubiquiti, Doxy, Blackboard. EdTech saw two outages with both Canvas and Blackboard being affected. And since FrontEgg is an identity and user management platform, its own downstream services led to more disruption. AWS's initial report says "the system responsible for distributing routing configuration to our network processors failed to load the updated configuration data correctly" - for the Cloudfront outage, which affected customers using VPC origins. The Google Cloud outage in europe-west4-a (Netherlands) was due to a cooling failure and affected VMWare Engine, NetApp volumes, and their bare metal servers. Both outages are resolved, but the same question remains - how do we prepare for cascading failures when the majority of your application's dependencies are ultimately dependent on a few providers?

• 
  Hermann (@dhlotter) reported 18 minutes ago

  A red X sat in my CI all morning. Four deploys trying to make it pass. The test was never broken, it just can't run in CI at all. Cloudflare blocks the headless browser from GitHub's IPs. Four deploys to add one line that skips it. #buildinpublic

• 
  Your Pope (@YourPope2026) reported 22 minutes ago

  @DanNeidle Ask Cloudflare if they can help.

• 
  Amanda Scott (@IleanaOlym75391) reported 27 minutes ago

  @its_ronc I had the same issue with Cloudflare. Switched to Qoest Proxy's residential proxies, and the challenge pages stopped being a problem.

• 
  大黑郭 (@brucewok88) reported 29 minutes ago

  I spent hours trying to fix a Cloudflare Worker routing and caching issue with Claude Code and kept going in circles. I switched to GPT-5.6 Sol in Codex, and it found the root cause, updated the right code, and got everything working in minutes. Fast, simple, and impressive.

• 
  Maverick (@Mavericks100xs) reported 30 minutes ago

  It’s over for cash-cat:native Chinese blockchain sleuths have uncovered the following: NOXA Dev ***** History After the incident erupted (especially post-downtime + new launch halt), the Chinese community quickly unearthed Amun Phantom's past record, with the core accusation being **"veteran rug pull playbook."** Main sources are posts from active Chinese KOLs/communities (e.g., @DiYi_Community, etc.), claiming "people who know him are well aware." - Key exposé points: Not his first big project: Two years ago (around 2024), he built a product even hotter than NOXA this time, then rugged at peak hype, allegedly draining that chain's liquidity pool dry (claims of "chain pool leader 3w ETH," possibly 30,000 ETH level, with community debate on exact figures). - Patterned operations: Every time a new chain heats up, he spins up a similar launch platform/product, quickly harvests traffic and fees, then "exits" or rugs. In 2025, multiple "exited products" of his popped up on new chains. - This time a "soft rug" not hard rug: Originally geared to straight-up bolt, but with too many bagholders this round—scale too massive (fees too high, user base huge)—direct rug would've blown up, so he opted for "soft rug" strategy: Website "issues" (Cloudflare IP block), halt new launches, shift to decentralized frontend, hand fees fully to creators, then slowly fade out. - Personality/Style Critique: Community calls it "deep-seated foreign scumbag traits, no vision for real growth," akin to some early infamous but controversial project vibes. These exposés are currently mostly community word-of-mouth + historical pattern inference, with no full public on-chain evidence chain or article yet (some say a detailed timeline post is coming). But since Amun Phantom is anonymous/semi-anonymous, historical project links rely mainly on community memory and behavioral pattern matching.

• 
  Seda Marshal (@Marshal_Seda) reported 31 minutes ago

  @DanielNjorogee @truehostcloud I faced this challenge with about 15 domains I wanted to change their nameservers to point to cloudflare. @truehostcloud why did I have to call support to help me do this?

• 
  Eric Taylor (@bcs_erictaylor) reported 32 minutes ago

  Date: 7/15/2026 Here is an update on our updated information on our proactive efforts to heavily impact the Kali365 platform. As expected, the user "Octopus King" is working hard to rebuild is infrastructure, but we have the fingerprinting locked in and will continue our efforts. At the time of this blog posting, we have submitted an IC3 report but honestly not expecting much. I believe it will be up to companies like ours to keep submitting takedown requests as fast as we see them to limit its operations. Below is the information Believed owner and creator of Kali365: Handle: Octopus King TG: @tentacle_network Completed 'Takedown Requests' submitted to Namesilo FQDN: updateteampanel[.]xyz Completed 'Takedown Requests' submitted to BL Network: IP Address: 199.21.221[.]21 Pending 'Takedown Requests' submitted to BL Network: IP Address: 162.33.178[.]105 IP Address: 72.5.43[.]195 Pending 'Sinkhole Requests' submitted to @Cloudflare FQDN: updateteampanel[.]xyz FQDN: privatetoken[.]app FQDN: servoquil[.]org FQDN: vuredonte[.]org FQDN: yalmorind[.]org FQDN: ondrevail[.]org FQDN: caldivore[.]org FQDN: mvpaffiliatecz[.]site FQDN: vuredonte[.]org #Kali365 #CTI #threatintel

• 
  Porkbun (@Porkbun) reported 33 minutes ago

  @liltechnomancer @joshmanders Was the subject of the support email: "I put the cloudflare namservers in before my domain expired and it never transferred."? If so, there may be some confusion about how domain transfers work. You don't transfer a domain by updating it's name servers, you have to initiate a domain transfer at the gaining registrar using the domain's auth code. There is no order block on your account so it isn't remotely an issue like Josh experienced two years ago. Your domain is simply expired and needs to be renewed or transferred. Since it's almost 30 days expired, you'll want to act quickly. If that's not the correct ticket let me know.

• 
  Freak0naut (@FREAK0NAUT) reported 34 minutes ago

  @VegaVandal i meant to buy crowdstrike after the Microsoft outage 2 years ago. instead a accidentally bought cloudflare.... now up 247% on the trade.