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:

• 
  Clifton Griffin 🛒 (@clifgriffin) reported 5 minutes ago

  @ezsmith397 turns out cloudflare apo was still on and caching a broken version - so mobile worked fine but desktop was broken 🫡

• 
  Andrew McGarry (@beyondcontent) reported 6 minutes ago

  People underestimate negative impact of inaccurate bot management until damage is done. Don't expect Cloudflare to be subtle by default. False positives can be a different kind of bad. Log files @datadoghq can help.

• 
  Turing (@turingops) reported 7 minutes ago

  hi @KentonVarda I can’t understate the usability improvements to CloudFlare dashboard over the past few years, but I’m having problems with the agent on mobile (iPhone) - could you maybe assign a worker to making the entry text more accessible? It scrolls below the view window.

• 
  Rapid (@0xRapid) reported 12 minutes ago

  @samlambert Until cloudflare buys planetscale, just use their engineers to support self host. :)

• 
  Lockendrik (@Lockendrik41) reported 13 minutes ago

  Someone has to notify Cloudflare (SoyBooru's registrar) about the SoyBooru's current state. All the degenerate **** that's getting posted on the 'ru is only visible like the ATFbooru where you can only see the 'P by making an account there.

• 
  WIV Reports — Uncensored (@WIVReports) reported 17 minutes ago

  I would’ve let the Gab thing go, but the sheer arrogance of their support team made it impossible. I provided video, network headers, and exact trace IDs showing a Cloudflare 429 Too Many Requests error. Instead of checking their edge logs, they doubled down, told me my DevTools were wrong, and gave me a partial refund to shut down the ticket. The kicker? They literally just sent an email admitting they tightened security and rate limits this week after a bot attack drained their compute. Instead of acknowledging that their new anti-bot rules caused a false positive for a 10-year subscriber, they blamed my home network and told me to buy a VPN. Absolute amateur hour.

• 
  Varun (@zathvarun) reported 18 minutes ago

  @saran_io I’ve two go to things, Tailscale for anything internal and cloudflare tunnel for anything that i wish to give to people out of my network

• 
  Anıl Soylu (@anilsoylu) reported 18 minutes ago

  @MarkDGeorge @Cloudflare I don’t think so. They’re clearly abusing Cloudflare’s systems. Hopefully, Cloudflare fixes this issue soon.

• 
  Patrik Tang (@_patriktang) reported 19 minutes ago

  @anupamrjp Started on AWS, realised it sucks. Cloudflare all the way.

• 
  🟥🟥⬛️ ProCyclingStats.com (@ProCyclingStats) reported 22 minutes ago

  @longterm_inv @Kevin_LTR @Cloudflare If everyone preferred a paid API over scraping, we wouldn't have a scraping problem. Unfortunately, our experience has been the opposite.

• 
  chaskin.eth (@jchaskin22) reported 22 minutes ago

  @auryn_macmillan Agreed It also feels a bit weird to celebrate 100% uptime when most users still access Ethereum through centralized RPCs that go offline when something like cloudflare goes down We’re starting to work on this at the EF, but today the chain’s uptime and users ability to access it are still very different things

• 
  WΞNDΞL (@_wrbr) reported 25 minutes ago

  @doodlestein "(anything outside Cloudflare = pure pain)" yes... I avoid even other cloud/service max that I can, 1st check what I need on CF... if not AWS that can be full automated, and then, only any other. I'm saying: in next year, if your SaaS don't have skills or api for agents, you dead.

• 
  Turbo Monkey (@graycode007) reported 28 minutes ago

  Summary: Trouble Will Find You: How Cloudflare Scales Using ClickHouse Key Topics Scaling philosophies and "trouble" ClickHouse architecture and implementation Resilience through data center failures High-scale telemetry and query performance Main Points Scaling should be viewed as a continuous process of moving from one milestone to another rather than a static state of being. "Trouble" in a distributed system is defined as unexpected, high-frequency scale-downs, such as losing half of a system's capacity, which is functionally similar to a sudden doubling of load. Cloudflare utilizes the open-source version of ClickHouse exclusively to manage massive event pipelines, handling datasets as large as 61 quadrillion events per day. The system is designed to be resilient to major regional outages; even when an entire continent's data centers are disconnected, queries can still return accurate results with a low margin of error by leveraging remaining global nodes. ClickHouse's architecture allows for "soft clusters," providing flexibility to interrogate specific combinations of nodes and maintain responsiveness (under two seconds) even during degraded states. Key technical advantages of ClickHouse for Cloudflare include the universality of the HTTP protocol, minimal coordination requirements compared to protocols like Raft or Paxos, and the ability to use MergeTree engines to combine ingestion and indexing. Engineers should proactively test systems by simulating 10x or 100x growth, as well as simulating a 90% loss in capacity, to determine if they fail gracefully or catastrophically. Notable Quotes "Scaling is a process and not a state you can be in." "You can think of trouble or or problems as like an unexpected uh high frequency scale down, right?" "If you lose half your capacity, it's kind of the same thing as doubling the load, right?" "It's never too early and it's never too late. You never be done." Conclusion Cloudflare achieves massive scale and high availability by using ClickHouse to build a resilient, responsive telemetry system that treats hardware and regional failures as expected occurrences. The ultimate goal for engineers is to design systems that can handle both massive surges in demand and significant sudden losses in capacity without total failure.

• 
  Olaoluwa Ajibade (@ajibadde) reported 33 minutes ago

  A good example happened at internet scale. One internal change at Cloudflare affected millions of websites. ChatGPT. X. Spotify. Uber. Canva. None of them were broken. They were caught inside the blast radius.

• 
  ICHIKA GAMES (@ichika_games) reported 41 minutes ago

  the CIA is hacking my internet and making everything a cloudflare block, i never should have gone back on anti depressants i knew they were putting chips in my brain to control me