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:

• 
  mental blanking interval (@vsync) reported 1 minute ago

  this happens when connecting via T-Mobile... @TMobile @rumblevideo @Cloudflare one of you fix this please

• 
  Marcus Gill Greenwood (@inventur_es) reported 2 minutes ago

  @FinlaysonConnor I don’t think the issue was whether Webflow was bad at what it did, the fact is web design is now both trivial and virtually free with LLMs. Hosting is also free (via services like Cloudflare) or very cheap. I actually think the pivot was necessary. Same with Wix but at least they got ahead of it with Base44 acquisition

• 
  timi2506 (@timi2506) reported 3 minutes ago

  @not_jpsenak @MyPayIndia It isn’t, it’s just Hauber who enabled cloudflare with PROXY mode 😭 (safari tries to upgrade to and cloudflare is like: “sure” just to display “server down” even tho it’s not)

• 
  Devanshu (@DevanshuXi) reported 4 minutes ago

  People usually learn tries in the context of autocomplete and dictionary problems, but once you start working on real infra systems, you realize tries are everywhere underneath modern high-performance networking and search stacks. I was recently reading the @Cloudflare blog about the performance bottlenecks of Linux BPF LPM tries used in packet routing and firewall systems, and learned something important. At scale, “search” stops being an algorithms problem and becomes a memory systems problem. The interesting part about tries is that they trade comparison-heavy searching for deterministic state transitions over bits/symbols. Instead of repeatedly comparing full keys like balanced BSTs or hash collision chains, a trie incrementally consumes the key itself during traversal. That sounds theoretical until you realize this is exactly why networking stacks use longest-prefix-match tries for CIDR routing. Routers are effectively doing millions of searches/sec over prefixes where latency matters more than throughput averages, branch mispredictions hurt badly, deterministic lookup depth matters, and memory locality dominates everything One thing that becomes super obvious from the BPF trie implementation is how “Big-O” alone becomes almost useless for understanding performance. The Linux BPF LPM trie uses only 2 child pointers per node, which means densely populated prefixes effectively degenerate into many sequential binary branch decisions. In theory the asymptotics still look acceptable. In practice, the trie height explodes, pointer chasing increases, and lookup throughput collapses as the structure outgrows cache and starts hammering dTLBs. That’s the part most people miss about high-performance systems: a cache miss is often more expensive than the actual computation. Modern CPUs are absurdly fast at arithmetic. They’re slow at waiting for memory. Also I was solving a suffix-query problem recently where the straightforward Trie solution itself wasn’t enough. The interesting part became optimizing the traversal and memory layout rather than just “using a Trie.” The strategy was to build a highly optimized reversed Trie where every node stores the “best” candidate index for that suffix path. Instead of doing expensive comparisons during query time, I pushed almost all decision-making into insertion time. While inserting container strings in reverse order, every node keeps track of shortest matching string and if tied, earliest index. So during query traversal, the search becomes almost embarrassingly simple: walk backwards through the query, follow pointers until traversal breaks, and the current node already contains the precomputed optimal answer. No heap allocations during queries. No suffix comparisons during queries. No backtracking. No secondary scans. Just incremental state transitions through memory. The funny thing is the actual algorithmic idea is pretty small. Most of the engineering challenge became memory optimization. A naive pointer-heavy Trie immediately started hitting MLE because every node carried 26 pointers. So the optimization was moving toward index-based contiguous storage: replacing raw pointers with integer child indices storing nodes in a flat vector, reducing pointer chasing improving locality, cutting memory almost in half And honestly this is exactly the same class of problem that appears in production systems. In CP, tries feel like string DS problems. In real systems, tries are actually cache-behavior problems disguised as data structures. That’s why production systems rarely use textbook tries. Instead you start seeing: Patricia tries, radix tries, crit-bit trees, compressed tries, LC-tries, succinct tries finite state transducers, double-array tries. All basically solving the same underlying issue: “How do we preserve fast prefix search while minimizing memory movement?” Even path compression itself is basically a cache optimization disguised as a data structure trick. So, This is why systems engineering feels so different from competitive programming sometimes. In CP, we optimize operations. In real infra, we optimize movement through memory.

• 
  Zack Riley 🇦🇺 (@ColdHeart_Prj) reported 4 minutes ago

  @BHolshouserUS Cloudflare went down earlier, probably had something to do with it.

• 
  Hekmon | Agent Workflows (@hhkkmon) reported 5 minutes ago

  I tried to save $20/month. So I moved part of my data from Supabase to Cloudflare D1. A few days later, D1 cost me $100+. The real lesson was not “D1 is bad”. The lesson was, I trusted AI-generated code because it looked correct. 😑😑😑

• 
  Saud Ilyas (@saud_ilyas) reported 6 minutes ago

  For the first time in 10 years, I moved the .io domain out of Namecheap to save $25 on renewal lol; never thought of moving any of the 2k+ domains I've managed with Namecheap for years. 3x the price is unjustifiable. Could potentially save up to $10k a year by moving every single one to Cloudflare on renewal. But that’s a very big headache doing one by one, so i’ll pass for now!

• 
  Fatima Yusuf (@fatimayusf) reported 7 minutes ago

  Huge effort by the team. Startups can now get up to $350,000 in credits on @Cloudflare. There’s never been a better time to build 🚀

• 
  Rufus (@Rufus87078959) reported 9 minutes ago

  @nooriefyi Are there any differences in service delivery between Vercel and Cloudflare?

• 
  baked beans (@beans1990) reported 15 minutes ago

  @DanielW_Kiwi Cloudflared* so you can tunnel from the service running on a host directly to CloudFlare.

• 
  Kelvinsekx (@kelvinsekx) reported 17 minutes ago

  @kristianfreeman @Cloudflare Do you guys have a service to host my vps?

• 
  Arosh (@AroshPererax) reported 19 minutes ago

  @_ashleypeacock @sudo_overflow The only thing is the latency. I think it’s probably because the workers are “region:earth” but my db is in one region. Even if i set worker to be in a particular region i am not sure if cloudflare treat it as a hint that will be respected when possible vs always.

• 
  cole murray (@_colemurray) reported 24 minutes ago

  @inababi @sudo_overflow no real resolution. “noisy neighbor”, which I don’t really believe as I’m seeing this across multiple client deployments historically, we used to call this “bad system design” @Cloudflare

• 
  Flaggy (@IRelievers) reported 25 minutes ago

  @sonemic be useful and stop using cloudfare I pay you money monthly and I cant even use your website cuz @Cloudflare is ran by sped 2nd graders who dont know how to run a bot blocking whatever ******** it is **** U

• 
  Ares (@miyagiyang) reported 25 minutes ago

  @brandonjcarl @Cloudflare I love your ideas. But It appears that Cloudflare does not support Python, which is widely used by agent developers.