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:

• 
  Vineeth K (@DealsDhamaka) reported 7 minutes ago

  Cloudflare lays off 1100 employees, about 17% of its staff. CEO Matthew Prince stated that efficiency gains from AI have made many roles, particularly in sales and support, obsolete.

• 
  moonboy (@Szypetike) reported 8 minutes ago

  @PaulGugAI Just use litellm it's a solved problem. The other side of the coin is either running your own open source models here nomad is positioned to benefit plus Nvidia or buy hosted model and here existing enterprise providers are going to benefit aws, azure, now cloudflare etc. plus Nvidia. However if 31b param models are the 80% workforce there's significant downward pressure on Nvidia et al in the medium and long term

• 
  siddharth (@sidpoasting) reported 8 minutes ago

  wanted to setup custom domains for my customers stores on my side project, since I use cloudflare so I thought maybe they should have a service to make it work and they actually have couple of them and it did work.

• 
  Massi — oss/acc (@0xMassi) reported 10 minutes ago

  I want to talk with people building AI systems that touch the web. RAG, agents, MCP tools, web scraping, docs ingestion, competitor monitoring, data extraction. What’s the annoying part nobody talks about? Stale docs? Noisy HTML? Cloudflare? Selectors breaking? Bad markdown? Search APIs? Crawlers? Chunking? Reply or DM me. I’m trying to understand the real workflows, not the polished demo version.

• 
  Rodolpho Arruda (@rodolpho_arruda) reported 10 minutes ago

  @catalinmpit Once I found by looking at the logs and having them processed by LLM that my VPS was being bombarded by local traffic inside the same datacenter (thus outside the Cloudflare tunnel). I opened a ticket and it was resolved. A kind of issue one could never imagine...

• 
  Rohde Builder (@felipe_rohde) reported 16 minutes ago

  Your competitor just launched a flash sale. You found out because a customer asked why your prices are higher. 😐 Cloudflare Browser Run's quickAction("screenshot") takes a pixel-perfect screenshot of any page on a cron — no browser, no infra, no drama. Diff it against yesterday's screenshot and you know EXACTLY when they: → drop a new promo banner 🎯 → launch a limited offer → quietly redesign their homepage → put your best feature front and center (rude) Visual change detection in one Worker call. No CSS selectors to maintain. No scraper breaking when they update their HTML. The screenshot doesn't lie. 📸🔥

• 
  Devanshu (@DevanshuXi) reported 17 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.

• 
  Marcus Gill Greenwood (@inventur_es) reported 20 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

• 
  sai prasad (@saiprasad03) reported 21 minutes ago

  @VFSGlobalCare Urgent assistance needed! My account is hit with a hard firewall block (Error 429001), preventing me from rescheduling an existing appointment. Customer support reset it earlier, but the Cloudflare proxy layer is still locking my User ID.

• 
  Hekmon | Agent Workflows (@hhkkmon) reported 21 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. 😑😑😑

• 
  Kenneth Eversole (@kennetheversole) reported 23 minutes ago

  @AskYoshik I ran all the Kafka clusters at Cloudflare, so I think I have a strong opinion about this. Kafka is an elegant design wrapped in a bunch of bloated crap.

• 
  Brandon Carl (@brandonjcarl) reported 24 minutes ago

  @miyagiyang @Cloudflare Thank you! You’re mostly right. They do support WASM-compilation and containerization, but that’s not a primary path, Not to over-evangelize, but the reason is rooted in how quickly they can spin up and down isolated JavaScript threads. It’s a reason why I was saying it requires thinking things about architecture. Before: I had to think, in terms of Kafka, Kubernetes, logging services, etc. Now those things are “free” - but requires revisiting application and other logic.

• 
  Lukasz (@woocassh) reported 24 minutes ago

  @arthuryuzbashew Not yet anyway, cloudflare still showing this domain in the dashboard and I already bought it with another provider. Wtf

• 
  PerceivingAI (@PerceivingAI) reported 26 minutes ago

  @idare Cloudflare free has so much value it's insane but I never thought about that use case. Fudge, now I have to have one. Maybe get a CF worker to be a sort of librarian and just throw all sorts of stuff at it. Turn it into a sort of well of knowledge for agents.

• 
  cole murray (@_colemurray) reported 29 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