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:

• 
  FiP MrMarki (@MrMarkilys) reported 3 minutes ago

  @SnowApe84586 @TrvthfvlTreason Cloudflare has allowed CP sites to be run whilst being protected by their DDoS protections. But the doxing* site are the bad guys. Doxing literally is public info, retard.

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

  There is no greater love than Christian hate. Gab, a company that constantly preaches its "Christian values" responds to a long term paying customer with pure disdain the second they get called out on technical incompetence. After dropping slurs and throwing a tantrum over standard DevTools logs, their CTO sent this email and immediately blocked my account on Gab so I couldn't reply. I am also sharing the email notification I received. Here is the full timeline of how Gab handles paying subscribers reporting a legitimate bug: 1: Socket io connections failed and looped infinitely, triggering a Cloudflare 429 Too Many Requests status code at their edge. 2: Support claimed a Cloudflare 429 signed by Cloudflare IPs was an issue with my "home Wi-Fi." A VPN on that same Wi-Fi instantly bypassed it, proving it was a server-side edge filter. 3: Instead of checking their WAF rules, their CTO claimed checking origin logs for 6 hours was "VIP treatment," accused me of using AI, and threw a fit. 4: I deleted my gab ai account, posted the DevTools receipts, and told him to fix his edge. 5: He sent a profanity-laden, slur-filled email, blocked me on the platform, and tried to hide it. Never once did I name-call or throw insults, I just posted raw HTTP response headers. This is how Gab treats the people who keep their lights on. Absolute amateur hour You can see the entire unfolding here on my X account, as I posted everything said verbatim. And again, here are the screenshots of the HTTP responses showing the issue is on them.

• 
  Apple Chomping Unc (@CigSmokingMill) reported 5 minutes ago

  Every social media app is throwing the Flock hysteria in your face. No one is getting banned, de-monetized, groups shut down, deflockdotorg shut down by cloudflare or ICANN, etc. That alone tells you all you need to know

• 
  Vinny (@hot_town) reported 5 minutes ago

  Damn. Cloudflare just became 100x cooler for me.

• 
  adam (@theCTO) reported 7 minutes ago

  never, we’re on @convex and @railway and @cloudflare everywhere, all at once

• 
  Swaraj⚡ (@botsboss) reported 8 minutes ago

  Current infra behind ytcrawl (Youtube Crawler) ✅ VPSs ✅ Docker Containers ✅ Docker Swarm + Portainer ✅ Proxy network / Terabytes of proxy bandwidth ✅ PostgreSQL ✅ ClickHouse ✅ Cloudflare R2 (planned) ✅ RabbitMQ ✅ Redis ✅ GitHub Packages (for container images/packages) ✅ Grafana

• 
  Ilya Gru (@ilyagruu) reported 11 minutes ago

  I bet complex frameworks such as @nextjs are going to lose ground because of AI. Modern browsers are very good now. Things like :has(), CSS nesting, container queries and import maps all work everywhere, with no build step. And every token an AI spends learning framework rules is a token it doesn't spend on your actual problem. Next.js now ships its own docs inside node_modules, with a note telling the AI: "your training data is old, read these instead." Also, some leaner alternatives can rise, such as: - Hotwire (made by 37signals, used in Basecamp) - Astro (bought by Cloudflare) - Plain HTML rendering + Hono.js - next AI's invented approach Boring is the new fast.

• 
  Lockendrik (@Lockendrik41) reported 11 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.

• 
  kirua (@aquipongoalgo2) reported 16 minutes ago

  @a63738464 1.1.1.1 as issa cloudflare service

• 
  Massive Clouds (@massiveclouds) reported 17 minutes ago

  @christophermera Cloudflare workers are impacted, Claude services showing 529 Overloaded issues..

• 
  IRONSCALES (@IRONSCALES) reported 17 minutes ago

  An email claiming to be Interactive Brokers told recipients their W-8BEN tax form had expired. Clean branding, right down to the NYSE, FINRA, SIPC footer. The Renew Certification button ran through the recipient organization's own link-protection wrapper, which reported it clean because the proxy loaded. The real destination was a domain registered the same morning the email went out, and it answered automated scanners with a Cloudflare challenge instead of a page. No history to score, nothing to render, verdict unknown. Themis weighed the convergence instead: a sending domain unrelated to the brand, a DKIM body-hash failure, a same-day destination hiding behind a bot check, and zero personalization sprayed across multiple mailboxes. Any one signal is deniable. All of them together are not. (Link to full teardown in comments)

• 
  John Spurlock (@johnspurlock) reported 21 minutes ago

  @CherryJimbo @Cloudflare @CloudflareDev growing in terms of customer usage etc

• 
  Gabe Fletcher (@gabefletcher) reported 22 minutes ago

  picks up phone dials 1800 @Cloudflare yeah hi. could you please fix the gateway for MCP authing, its currently more dead than a day 30 day old vibe coder and cant auth anything. okthx

• 
  Alex Veremeyenko (@alex_verem) reported 22 minutes ago

  Cloudflare's CEO predicted bots wouldn't outnumber humans online until 2027. it happened in June. multiple cybersecurity firms confirmed it this year, each with their own data. Cloudflare says bots now generate 57.5% of all webpage requests. Thales, the French defense and data security group, dates the crossover even earlier and puts bot traffic at 53%. nobody can agree on when it happened because no single provider sees the whole internet. but every provider that looked found the same answer. and the composition changed. AI training crawlers still make up 67.5% of AI-driven traffic, but they're a shrinking share. the fastest-growing category is AI agents that click links, fill out forms, and mimic human browsing behavior. that segment grew 7,851% year-over-year according to HUMAN Security. that's when it gets uncomfortable. every ad impression, every conversion funnel, every analytics dashboard on the internet runs on one assumption. a human is on the other end. pageview-based monetization only works when the visitor is a person. when the majority of visitors aren't people, that model breaks. and it's already breaking in ways nobody can measure. bot-detection systems misfire on real humans at rates of 7-15%, and agentic browsers that mimic human behavior slip past traditional filters. engagement numbers go up, bounce rates go down, and no analytics tool can tell you how much of it is real. Stripe says 70% of its developer tool commands now come from agents. 25% of developers already design APIs with agents as the primary consumer, not humans. but the contradiction underneath is obvious. agents make up 57.5% of the traffic and roughly 1% of the economic activity. nobody has built the payment and liability layer for machines yet. agents can browse the entire internet but they can't buy anything on it. dead internet theory was a fringe conspiracy for over a decade. it became a measurable fact faster than the CEO of the company best positioned to track it expected. the question worth asking isn't whether bots outnumber humans online. that's settled. it's what an internet built for human attention is worth when most of the attention isn't human.

• 
  The Hacker News (@TheHackersNews) reported 25 minutes ago

  The attacker’s own server address never appears on the wire. msaRAT uses Cloudflare to establish the connection, then routes the entire WebRTC channel through Twilio. Defenders see the victim’s browser talking to legitimate services. No Chrome or Edge patch fixes this. It exploits neither browser. Hunt for Chrome or Edge launched by an installer, service, or another non-interactive parent with --headless=new and --remote-debugging-port. See “Hunting Notes” in the article.