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:

• 
  Abhi Bavishi (@abhibavishi) reported 3 minutes ago

  I moved @SmartifyIndia off WordPress last month. Honestly, the trigger was embarrassingly simple. Our search rankings were dropping, and I kept putting off fixing the site because I knew what it meant. Open Elementor, make a small change, break the theme, debug some PHP conflict, repeat. It was hell every single time. So I just... didn't. And the site kept suffering. Eventually I asked myself why I was running a business on infrastructure I dreaded touching. So I migrated to Astro + Cloudflare Pages using Claude Code. The entire site is now pre-built at deploy time. Every page is a static HTML file served from Cloudflare's edge network. No server. No CMS login. No PHP. No database queries on page load. No plugins to update. No attack surface. Hosting costs went to zero. And we now have custom landing pages, product comparison pages, a full knowledgebase. Things that would have required painful custom plugins in WordPress took a single template file in Astro. I'll be honest though. The migration wasn't a clean win from day one. Google was only indexing about 33% of the pages initially. Fast static files aren't enough if the content is thin. We had to go back and actually make pages worth indexing. WordPress made sense in 2008. In 2026, for a business that primarily publishes content and captures leads, it's mostly just weight. Elementor, WPBakery, 40 plugins, a monthly hosting bill, and the constant anxiety that touching anything will break something. I was holding on to it because migrating felt hard. But I was paying for that laziness in rankings every single month.

• 
  Rahkyt Redux (@rahkyt) reported 9 minutes ago

  Stopping the bad guys with Cloudflare: 6,563 malicious requests blocked or challenged in the last month #cloudflare

• 
  Diego Artiles (@dartilesm) reported 12 minutes ago

  Cloudflare Workers used to run in front of the cache. Now they can run behind it. Workers Cache: one wrangler.jsonc line. Worker never runs on a cache hit — no CPU charge. Does this change how you'd design a Workers app?

• 
  Samian (@ApplyWiseAi) reported 17 minutes ago

  @QuinnyPig @Cloudflare the "ask the customer what they want" trap is such a cop out. cloudflare just ships a sensible default and moves on. that's the whole difference.

• 
  Duyet (@_duyet) reported 18 minutes ago

  @born2code @CFchangelog No, Cloudflare Tunnel is not gone. The service (including Cloudflare Tunnel for SASE and Cloudflare Mesh) continues to operate normally. Only two specific legacy API elements are being retired on October 5, 2026: • CIDR-encoded route endpoints in the Zero Trust Networks API (replaced by modern route_id-based endpoints). • The connections field in tunnel list/get responses (you must now use dedicated per-tunnel connections endpoints instead). These changes make API responses smaller/faster and bring consistency to how resources are identified. (By Grok)

• 
  Dmonty (@Dmonty28516998) reported 19 minutes ago

  @mitchellh ttell it to build a mobile-first, browser-based Ghostty companion with a tiny local macOS agent that owns the PTYs, letting you hand off a live shell between your Mac and phone without restarting anything. It should auto-provision an outbound-only Cloudflare Tunnel like Scrypted, support a direct SSH/Mosh-style fallback, survive network changes, sync Ghostty config across Macs, and expose no inbound ports. Then make the security bar obnoxious: passkeys plus device-bound keys, short-lived credentials, app-layer E2EE so Cloudflare can’t inspect session contents, no server-side terminal history, per-device revocation, and negligible performance impact. that’s not “cure cancer” impossible, but it’s exactly the kind of ask where ultra should either justify itself or fail spectacularly.

• 
  metal gore solid (@shartdotcloud) reported 19 minutes ago

  i get more out of my 5 dollar cloudflare workers plan than the thousands i have spent on AWS over the years. they are so responsive to customer feedback. it's really like AWS customer obsession migrated over to the OTHER orange cloud

• 
  2xnmore (@2xnmore) reported 19 minutes ago

  Right now, while your eyes move across this sentence, something out there might already be pretending to be you. Not someday. Not in some distant future. Right now, while you're reading this. More than half of everything moving through the internet is no longer human. Cloudflare put a live number on it. 57% bot. 43% human. Their own CEO expected this in 2027. It arrived eighteen months early, and by his own admission, it stunned him. Sit with that for a second. Somewhere tonight, a machine is filling out a form using a stolen photo of someone's face. Somewhere tonight, a machine is opening an account nobody authorised. Somewhere tonight, a machine is trying to move money out of an account that isn't its own, using nothing but a convincing enough copy of a human being. And here's the part that should actually scare you. If more than half of every login could already be a machine wearing a human's face, what happens the next time your bank calls to confirm your identity? What happens the next time your vote needs verifying? What happens the moment someone builds a fake version of you good enough to fool the system standing between your money and whoever wants it? Most systems built to stop that are still asking you to prove who you are with things that can be stolen. A password. A photo ID. A database entry sitting somewhere, waiting to be breached. One team already saw this coming. Quietly. Inside Bittensor. Thirteen months ago. It's already live, and almost nobody outside a small circle has heard of it yet. Full breakdown below. Most people just found out too late. @opentensor $TAO

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 22 minutes ago

  @CodeWithZeee every company i've worked at that used cloudflare: they tried to charge us between $3k/mo - $10k/mo based on whatever number their sales team pulled out of thin air at the same time we were having serious reliability issues on them at the time had no choice and ponied up bc we were vendor locekd

• 
  TigerBandit (@EucalyptusG) reported 22 minutes ago

  @csoandy @eastdakota I'm a long-time Cloudflare customer and love the product, but I couldn't care less about your appeal to authority. Dodging the facts without engaging just shows your ignorance and disregard for the actual discussion. Building a CDN does not make you an expert on privacy laws.

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 25 minutes ago

  The fix: → Blocked the IP range in .htaccess and CSF firewall → Added rate limiting via mod_ratelimit: 100 requests/minute per IP → Enabled Cloudflare Bot Fight Mode (free on all Cloudflare plans) → Added robots.txt rules to block known commercial scrapers → Enabled Cloudflare's "I'm Under Attack" mode for 24 hours Bot traffic: dropped to near zero within 4 hours. Bandwidth: back to normal the next week.

• 
  SHELBY (@Precious_Ngan) reported 25 minutes ago

  If the website uses a CDN (Content Delivery Network) server like Microsoft Azure CDN, Fastly or Cloudflare, the DNS server will send the IP address of the CDN server instead of the website's original IP address.

• 
  Shinjae Kang (@zemnanet) reported 28 minutes ago

  A Worker deploy can now carry the versions your app actually installed, not just package.json ranges. That makes dependency drift a release-handoff problem. Which artifact would you review first: lockfile, CI log, or upload receipt? #cloudflare

• 
  Cesar A. Nogueira 🇵🇹🇧🇷 (@cesarnog_eu) reported 33 minutes ago

  Stopping the bad guys with Cloudflare: 202 malicious requests blocked or challenged in the last month #cloudflare

• 
  Anurag (@Malwarehunterr) reported 36 minutes ago

  Site impersonates Patreon and steals the victim's email and password, exfiltrating them to a Telegram bot. URL: pat-re-on[.]site It then requests a 6-digit verification code, but accepts any random code and redirects the victim to URL: log[.]brunaecass[.]com The second stage loads a Gmail login page using Cloudflare Turnstile, Microsoft SignalR, canvas rendering, and anti-analysis features including DevTools blocking and navigation interception. IOCs: pat-re-on[.]site log[.]brunaecass[.]com log[.]brunaecass[.]com/9730502/index log[.]brunaecass[.]com/9730502/HubStream log[.]brunaecass[.]com/9730502/window log[.]brunaecass[.]com/9730502/intercepts.js Telegram Chat ID: 8619867034 Telegram Bot ID: 8747484284 #Phishing @500mk500 @skocherhan