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:

• 
  Patrick Ryall (@PadraigOraghail) reported 5 minutes ago

  The learning is never ending. Mostly it is platforms, in this case using Cloudflare as the auth gate. I had never used cloudflare for more than DNS. Now I have three sites running on it, for free, which is mad. Workers, Zero Trust, DNS, connected to ***. It's all rather slick.

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 6 minutes ago

  @Cloudflare Fix human verification

• 
  Deyder Cintron (@deydercintron) reported 8 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.

• 
  Kyle Avery (@kyleavery) reported 9 minutes ago

  @wongmjane @Cloudflare finally, i won’t need 3 workers for each service 🙏

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 12 minutes ago

  @Cloudflare Fix human verification

• 
  Villainess of Resevoi (@GalCharoShipper) reported 14 minutes ago

  @Tepafray @Sean_Topic AI crawlers simply ignore ****. Even layered defenses recommended by artist-protection groups (Glaze for image-level noise, Cloudflare-style bot blocking, watermarking, opt-out registries) are described as a partial, constantly-shifting arms race, not a solved problem

• 
  JP (@jpshrodinger) reported 14 minutes ago

  my site had a react hydration bug for WEEKS checked my code 100 times. rewrote providers. nothing it was cloudflare. it rewrites email addresses in your HTML to "protect" them and breaks react silently the bug was never in my house

• 
  pkuseri (🍉) (@Pkuseri_) reported 17 minutes ago

  @stupidtechtakes Do you know any better alternatives aside cloudflare? Not being rude or anything if the tone sounds rude mb

• 
  David Oks (@davideoks) reported 17 minutes ago

  @inoutremer @CharlieTyson1 this type of thing is solved by hosting on e.g. Cloudflare. pieces going modestly viral like Wilson's or Oyler's did shouldn't crash a modern web site! presumably they just have terrible IT. (but a quite wonderfully designed website IMO)

• 
  Saeid Shahriari (@saeidshahriari) reported 19 minutes ago

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

• 
  🍄 DO NOT FOLLOW TIMO 😈 (@liltechnomancer) reported 22 minutes ago

  @thdxr Because you have process issues. If you didn't extensions would work on cloudflare.

• 
  Kevin Minnelli (@minnelli) reported 23 minutes ago

  WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

• 
  siftydeals (@siftydeals) reported 25 minutes ago

  Cloudflare had 487 outages in H1 2026. Most teams still treat uptime like a technical metric instead of a customer trust issue. Your SaaS tool only works if your customers can actually reach it. 🔧 Details in link.

• 
  🔥🏴‍☠️CyberTechWolf🏴‍☠️🔥 (@CyberTechWolff) reported 26 minutes ago

  @ChaoticTKnight I'm gonna laugh if Cloudflare gets DDOSed or some **** because they wanna claim the Internet. Not everyone has to be hijacked by Cloudflare and I hope someone hacks their ******* **** I don't use these words a lot but the Internet might just have robophobia.

• 
  Selenka (@SelenkaOnChain) reported 29 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."