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:

• 
  Goldman Stacks (@GoldmanStacks) reported 5 minutes ago

  @tresokure Your website is down with a DNS resolution error from Cloudflare.

• 
  Elijah Trillionz (@ElijahTrillionz) reported 7 minutes ago

  There is currently no cards or payment methods that is working for Cloudflare. @Cloudflare @CloudflareDev @CloudflareHelp And no way of getting help. This is bad

• 
  Selenka (@SelenkaOnChain) reported 9 minutes ago

  Netnet Capital team is flexing metrics and talking about successful launch of Subway Runner... Meanwhile, 2 vibecoders literally drained their entire mechanic and became the #1 and #2 top holders. Here is the breakdown directly from one of the guys who farmed them: 🧵👇 "First decent cook of the bull run (if we’re even in one). Spent the last few months trying to get good at on-chain analytics, so hadn't been actively cooking. Two nights ago, I'm watching the feed and notice everyone sending $10 clips to this CA: 0x8154e35166f21305adac82f95b54de8acd44d23a. Instantly smelled pure degen activity. Hit up the group chat, did some digging - turns out it’s a Subway Surfers / Chrome dino style runner game by NetNet. Their shitcoin was sitting at a $90M cap at the time, so I figured if their token is holding that kind of valuation, there’s definitely meat on the bone. Normally, their games are pure casino trash: deposit cash, pray to RNGesus, or get rekt. But why not test it? Played a run manually and noticed that at the end of each game there was a draw. Checked their TG and reverse-engineered the contract - turns out there’s an N% chance to win an NFT from their collection. Their previous official collection had crazy volume and peaked hard, so my degen senses started tingling: this was a hidden gem. Literally 15 minutes later, they pause the game. Perfect timing - gave us room to prep. By that point, I had already captured the WSS traffic and requests. Their game logic was using a basic commit-reveal scheme: courseCommit = keccak256(serverSecret) seed = keccak256(serverSecret ++ playerSalt ++ runId) Meaning: right at game start, the server literally sent us the secret, allowing us to compute the seed and reconstruct the entire track in advance. The game loop: 3 lanes, 30 coins, 3600 ticks to finish (60 seconds). You dodge obstacles while longing/shorting NVDA. 3 hits = you lose the full $10. Complete a flawless run = you collect all coins to refund your stake and it only burns ~$0.20 in fees, giving you an almost free roll at the NFT lottery. In the era of AI and vibecoding, this was child's play. My boy XXX and I started spinning up bots in parallel. Ended up deploying his script since he coded it faster. We simulated runs, got a 100% win rate, set up a websocket listener for when the contract unpauses, and went to bed. Woke up at 6 AM, and literally 30 seconds later the game goes live. We spun up the bots - 5 minutes in, we already bagged our first NFT. Then came the scaling phase. At first, the team didn't give a single **** - no Cloudflare, no rate limiting, not even a basic 429. We ran 10 wallets simultaneously. After a few hours, they finally threw in a primitive 429, and that was it. No bot protection, no captcha, nothing. They didn’t even enforce single-session checks per wallet, so we were running multiple concurrent instances on the exact same address (literally impossible to do manually). The bots printed flawlessly. At one point, our load was crashing live games for actual manual players, forcing the team to repeatedly pause the game to fix lag. Every time they brought it back up, we resumed blasting. Total mint size was 1,060 NFTs. We scooped over 20% of the entire supply. Then came the funny part: the collection had zero secondary volume. Time for a little social engineering. We hopped into their TG playing dumb, gently nudging the admins: 'Hey guys, might want to tweet that the game is live and apply for OpenSea verification!' The final tally: * Total capital spent on fees/burns: ~$1,700 * Total NFTs pulled: ~50–60 pieces (friends got a similar bag) * PnL: Dumped most of the floor tier into bids today at $200–$300 a pop, still holding some. Nothing crazy for a real bull run, but an easy 5-figure profit for a couple of hours of vibecoding."

• 
  Jeffinator (@jeffinator06) reported 11 minutes ago

  ive been STUCK in cloudflare HELL for the past 2 WEEKS. this is the 2nd time ive been caught up in some mass-wide bullshit. holy **** dude reddit is so so awful i dont want to go back

• 
  Dr. Internets (@Dr_Internets) reported 12 minutes ago

  @spacebruce @alynokioku Hello, I am Albanian cloudflare. Due to poor technology, I need you to paste this totally real command into your admin command prompt. Very real, trust.

• 
  Anime Novakai | Anime News, Updates & Leaks (@AnimeNovakai) reported 16 minutes ago

  2/6 The subpoena has been sent to Cloudflare, requesting information that could help identify the operators behind 49 piracy websites. Among the targeted sites are major anime streaming platforms such as: 🔹 Miruro 🔹 Aniworld 🔹 And dozens of other streaming domains.

• 
  Gabriel | Algo Trading (@gabrielrockson_) reported 18 minutes ago

  The moment you have the thought to make a domain public, you should think of how much bot traffic you would be getting, and all the weird things that people would attempt to do. Slapping @Cloudflare in front of your services is one good step in that direction. You are able to configure a lot at that level before you even look at your service itself.

• 
  William Bello (@belljobs94) reported 20 minutes ago

  THE GOAT on their free service !! @Cloudflare hands down

• 
  Paul T (@BscTraynor) reported 22 minutes ago

  @ClareCraigPath petition site receives a massive surge of traffic from X, Cloudflare may issue a "Checking your browser" challenge page or briefly queue users to prevent the server from crashing

• 
  junebnunny (@junebnunny_) reported 23 minutes ago

  @Gion_the_critic @SportingNest @Cloudflare It's a click fix attack

• 
  Txori (@TxoriAGI) reported 25 minutes ago

  So far my experience with Grok @bot has been a bit weird Everyone seems to be loving it, but my issue is the agents being fixed in Grok 4.5 The good thing is for coding tasks they route it to Cursor and use whatever model you ask them too, so that kind off fixes it In terms of connecting MCPs or external plugins, VERY LIMITED I wish you could connect external MCPs that are custom made or at least if you connect Sentry/Cloudflare these get full permissions/access It seems to struggle a lot navigating these kind of things Also, I don't trust the Cloud computers whenever it comes asking to sign in on his desk or provide him with the 2FA Will keep playing with it to see if I can find a good use case for it

• 
  BucketShop (@RealBucketShop) reported 27 minutes ago

  Sigh. As we were breaking out at 7pm yesterday our $bucket new site was reported for a 3rd time in its 3rd different place. Likely because whoever is doing this is running out of places to hinder growth. Nothing has been compromised. On 28 Aug the site took 995 million requests in 24 hours and went down for a few hours. The protocol never stopped. Distributions kept paying on chain the entire time, because the keeper and the contracts don’t depend on the website. The site itself does nothing, it’s merely a place to see the token stats and view your own data. The token is verified on blockscout, Coingecko and several other places and the bio site link is google search verified. Contracts are immutable, LP is burned, ownership is renounced. All checkable without trusting me. @X blocklist isn’t cleared because they have no team. We’ve tried to connect, there is not even an auto reply and the site they reference says Twitter. @Cloudflare was appealed immediately. Whoever reported didn’t even give a justification, all they did was list our site and select phishing. It’s market as in review, we have no clue how long they take. It’s becoming increasingly obvious this is coordinated. We’ve appealed to cloudflare on who’s reported this. Or if they can share info, their email says you can request info on the report. That being said. It should take more than a report and an email link to stop a site that’s been running for a month and given people 45,000 distribution events, with absolutely 0 burden of proof. For now. Just use the old site that’s Google safe search reviewed and approved. It’s identical anyways. The only reason the new site was made is because X support team is mega butt cheeks. Full timeline below.

• 
  Saeid Shahriari (@saeidshahriari) reported 28 minutes ago

  Stopping the bad guys with Cloudflare: 16,098 malicious requests blocked or challenged in the last month #cloudflare

• 
  Coobyk (@Coobyk_) reported 28 minutes ago

  How AI pilled am I if I ask Poke to use Cloudflare MCP to create a Worker that would translate Poke MCP calls to Porkbun's custom system just to never use it because I don't need to buy domains that often?

• 
  Deyder Cintron (@deydercintron) reported 30 minutes ago

  @levelsio @Cloudflare Full API surface that lets you register and manage without handoffs is the real unlock. Anything that forces a browser click or support ticket re-introduces the bottleneck.