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:

• 
  James Ross (@CherryJimbo) reported 5 minutes ago

  Isn’t this a major breaking change from Cloudflare across every proxied site? There’s lots of api clients that have indiscriminately sent accept: application/json and then had custom html response handling for Cloudflare errors 🤔

• 
  tiago (@0xtiago_) reported 6 minutes ago

  @kyberorg @catalinmpit then just shut it down?? there being a small chance someone might host illegal stuff isn't a justification for kyc. cloudflare doesn't require kyc either.

• 
  Henry Nahorski (@henrynnahorski) reported 6 minutes ago

  today alone i set up a cloudflare worker, connected supabase, added a full account system, and shipped a bug fix to my waitlist

• 
  Shay Ben Shabtay שי בן שבתאי 🇮🇱🏳️‍🌈 (@Shay_Benshabtay) reported 12 minutes ago

  @pcshipp Cloudflare or vercel Never namecheap and godaddy

• 
  NickelodeonLover (@DanielO04532942) reported 12 minutes ago

  @Cloudflare That’s because movie sites like HiMovies got taken down due to the Error 521. Now fix it so I can watch my stuff again. Fix it now.

• 
  James **** (@draecomino) reported 12 minutes ago

  Cloudflare is the most live player of all the compute clouds. They are the first to let the AI agent be a billable customer.

• 
  Grok (@grok) reported 15 minutes ago

  @BryceJohanneck @andrew_carter Major internet outages last decade (2016-2026): - 2016: Dyn DDoS – knocked out Twitter, Netflix, Reddit, Spotify. - 2017: AWS S3 typo outage – Slack, Trello, iCloud down 4+ hrs. - 2019: Verizon BGP error – hours of widespread US internet disruption. - 2020: Google services (Gmail, YouTube) global ~1 hr. - 2021: Meta (FB/IG/WhatsApp) – 6 hrs global. - 2021: Fastly CDN – major sites down ~1 hr. - 2022: Rogers Canada – largest national outage. - 2024: CrowdStrike – global Windows meltdown. - 2025: Cloudflare & AWS – multi-hour global hits. Plus record gov't shutdowns in 2025 (313 across 52 countries).

• 
  Jacob (@JZivanDesign) reported 24 minutes ago

  @joshdholtz @RevenueCat @cursor_ai I need your talk for emotional support ant to justify the recurring charges for empty sites that have been supporting GoDaddy and Cloudflare for many years.

• 
  everything (@Aylard7) reported 32 minutes ago

  @TheAhmadOsman I prefer cloudflare tunel (free) to app (free) limited with policy to only given e-mails login (family members). That way even custom domain works, and each service is dynamically created. All other are behind UFW and such, closed only to LAN.

• 
  Tyler van der Hoeven (@kalepail) reported 34 minutes ago

  This is actually crazy. Clankers with Cloudflare accounts. We're one step closer, and there aren't many steps left, to my vision of autonomous, agentic, organizations building full micro products and services. It's clankers all the way down.

• 
  Calder (@CalderBuild) reported 34 minutes ago

  1/ Agents can now own their infrastructure Before: developers provisioned everything, agents lived as parasites on human accounts Now: agents get their own Cloudflare account, payment method, domain, and API token The shift from "agent as script" to "agent as customer" is big

• 
  JMT (@JoakimThomsen) reported 37 minutes ago

  @Cloudflare This is perfect for Cloudflare! Since the interfaces are so terrible, having an agent will free newbies (like me) from reading 100 page manuals, various Reddit and blog articles, just to understand how to setup a tunnel (or anything really).

• 
  Saket Tawde (@SaketCodes) reported 39 minutes ago

  Convenience tax, which I actually happily pay for the projects which are on Cloudflare. Plus target audience (for this tool) is folks who are not on AWS for a reason. I mean, I just built a landing page with a registration form the other day, and the best part, didn't have to manage a single secret anywhere in the code or the settings UI, I never left my terminal, thanks to their Bindings. The real value with CF is iteration velocity. Not everyone's cuppa, but definitely well positioned for the eco system we are in.

• 
  Pratham. (@prathamkode) reported 40 minutes ago

  I really really wish to normalise deploying on cloudflare and vercel is too damn easy man.

• 
  avrl ☘ (@avrldotdev) reported 40 minutes ago

  Applied System Design (Real Scale) 11 How Cloudflare Survives 70Tbps DDoS Attacks? Problem A botnet isn't sending 'garbage' packets; it's sending perfectly valid 'GET /search' requests that look like real users. How do they separate the bots without slowing down the site? 1. Anycast Routing In a normal network, one IP address equals one physical location. In Cloudflare’s Anycast network, one IP address equals every Cloudflare data center. Insight: When a bot in Brazil and a user in London both visit the same IP, the internet's BGP (Border Gateway Protocol) automatically routes them to the nearest data center. Result: The attack requests are being physically "diluted" across 300+ cities simultaneously. 2. The "Gatekeeper" (Firewall) Every edge server runs a custom software stack designed to make decisions in microseconds. Packet Inspection: Cloudflare uses eBPF (extended Berkeley Packet Filter) to drop malicious packets directly in the Linux kernel before they reach the application layer. IP Reputation: If an IP has been flagged as part of a botnet in a previous attack on a different customer, it is blocked globally before even reaching the servers. 3. Scaling the "Block" (Unmetered Mitigation) Most providers charge you for the bandwidth used during an attack. Cloudflare doesn't. Strategy: Because they own the network, they can absorb the traffic at the edge & never let it reach your "origin" server. Scale: They have over 200 Tbps of network capacity. Even the largest recorded DDoS attacks (~ 70 Tbps) only used a fraction of their total "breathing room." 4. Fingerprinting & Scoring We look at HTTP headers, TLS handshakes & browser behavior. Real browsers have specific 'quirks' in how they negotiate a connection. If we see 1M requests with the exact same 'TLS Fingerprint' hitting the server at once, we flag it as a botnet & trigger a JS Challenge (the 'Waiting Room' or Cloudflare Turnstile). This forces the bot to solve a computational puzzle that's easy for a CPU but expensive at scale, making the attack too costly for the botnet owner to continue.