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:

• 
  TechRemarker (@TechRemarker) reported 5 minutes ago

  @CloudflareHelp @Cloudflare @eastdakota After about 10 minutes if using the throttle feature to reduce page speed to a kb, and disabling and re-eanbling was finally able get the billing submit case screen to stay up just long enough to paste in the info and click submit. God help anyway else trying to reach billing.

• 
  Tejas (@stejas809) reported 5 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

• 
  Lilith Datura (@LilithDatura) reported 6 minutes ago

  @Rolando_tillit OK, this is interesting because I’ve been kind of approaching this from a different angle with something. I’ve been trying to bring people’s attention to with Anna’s archive and Suno and some of the other stuff that happened since December. I’ll circle back on it. “He paired it with the observation that Cloudflare (a major CDN, proxy, and security provider for a huge share of websites) “regularly memory holes stuff.” Cloudflare itself does not host most content it protects—it sits in front as a reverse proxy and generally forwards abuse reports—but it can and does take action on content it does host (Pages, Workers, etc.), enforce blocks, or contribute to sites becoming unreachable when combined with origin decisions, domain issues, or legal pressure. The broader point is that the popular idea “the internet never forgets” is incomplete: platforms, operators, hosts, and infrastructure providers can and do make material harder or impossible to find, turning once-prominent corners of the net into footnotes or ghosts.”

• 
  Publisher in a Box (@publisherinabox) reported 7 minutes ago

  The median company shows up in just 16% of relevant AI answers. It earns a citation with a link only 6% of the time. That is the new scoreboard, and almost nobody is ready for it. Webflow analyzed 2,000 websites for its AEO Maturity Index and found the gap is not some exotic AI problem. The underperformance traces back to broken links, missing metadata, and stale content. Basic SEO failures are now GEO failures. Companies that scored higher on GEO readiness saw 2x higher mention rates, 60% higher citation rates, and 80% higher share of voice in AI search. The volume is already there. DataDome recorded 17.7 billion AI agent requests in Q2 2026 across 400+ companies, up 45% from Q1, and Decodo's read of Cloudflare data puts automated systems at 57.4% of all web requests. Publishers have largely stopped treating AI answer engines as a referral source. Mentions and citations are the currency now. Clicks did not disappear, but the strategic work moved from chasing page views to controlling how AI surfaces your content. LLMs.txt is not the shortcut. Adoption grew from 4,088 instances to 36,120 in a year, and Ahrefs server-log research found 97% of those files received zero requests in May 2026. Google's own guidance says the file is not necessary for generative AI search optimization. The takeaway for publishers building diversified businesses: GEO is not optional and it is not complicated. The win condition shifted from traffic to citation, and the barrier is not new technology. It is the same fundamentals that have always mattered. Clean metadata, fresh content, working links, structured answers to real questions. Most publishers have not audited for this yet. That is exactly the gap.

• 
  Anurag Bhatia (@anurag_bhatia) reported 11 minutes ago

  @nileshgr @Cloudflare They are known to be one large dns resolvers who does not support ECS (besides quad9 on their main 9.9.9.9 as well). That will always impact Akamai traffic. Part of it also bad design by Akamai end for relying so heavily on dns for mapping.

• 
  Gavin Keulks (@GavinKeulks) reported 16 minutes ago

  @DrDavidVernon @britishlibrary Thank you for those kind words. The site was severely damaged by a server upgrade at my university, and for years I thought it was gone forever. Thankfully, repair (albeit tedious) has been possible. Now I've taken full ownership of all aspects of the site, so if it's damaged again, it will be because Cloudflare accidentally shut down the internet again (as it did a few years ago).

• 
  Invader Zim (@spiralout112) reported 20 minutes ago

  @dhh @Cloudflare I did go down the dns benchmarking rabbit hole, and cloud flare definitely did win.

• 
  Rob Hallam (@robj3d3) reported 21 minutes ago

  If you wanna do it yourself, this is how: Buy (~15 min) 1. Cheap VPS from Hetzner or DigitalOcean (~€5-10/mo), Ubuntu 24.04, tick automatic backups at checkout 2. Add your domain to Cloudflare (free plan), switch nameservers at your registrar 3. Install Termius (SSH app) + Tailscale (private network) on laptop and phone, free tiers Lock it down (~20 min) 4. Generate an SSH key in Termius, add it to the VPS at creation. Keys only, never passwords 5. SSH in once via public IP, run updates, install Tailscale on the server, log it in 6. Disable Tailscale key expiry for the server (admin console, one click) 7. Verify you can SSH via the server's Tailscale 100.x address BEFORE the next step 8. Provider firewall: delete all inbound rules, allow only port 443 from Cloudflare's published IP ranges. No public SSH at all. You enter through the tunnel 9. Test from outside: public IP times out on everything, Tailscale IP connects. Server is now invisible 10. One SSH key per device. Phone gets its own key added to authorized_keys Install the brain (~5 min) 11. apt install tmux then install Claude Code (official native installer, one curl command) 12. Run Claude Code inside a tmux session so it survives disconnects and keeps working while your laptop is closed Hand over everything else 13. Write ONE long handover prompt telling Claude Code: the server facts, the security model (so it doesn't "fix" it), folder conventions (/srv/ per project, one tmux session each), your preferences, and standing rules (confirm before destructive actions, new services bind to localhost/Tailscale only) 14. Make it write all of that into CLAUDE.md first, so every future session already knows everything 15. Backups before features: nightly job pushing your data to GitHub, tested, before a single page exists 16. Then let it install the web server (Caddy + Cloudflare DNS plugin plays nicest with the locked firewall), set up SQLite, deploy the first page From then on you never administer the server again. You open Termius from anywhere, on any device, and just say what you want. BOSH

• 
  the Sleeping Wizard (@magicnaptime) reported 21 minutes ago

  Damn guys maybe try dialing it up to 2:2:2:2 for Pete's sake @CloudflareDev @Cloudflare

• 
  TezaApps (@TezaApps) reported 21 minutes ago

  @idunnstudio Good catch running the audit anyway. Stripe's restricted keys are the other half of that fix, a leaked key that can only read is a bad day instead of a disaster. Mine lives only in a Cloudflare Worker so the client bundle never even sees it.

• 
  pcstyle (@pcstyle53) reported 22 minutes ago

  @stupidbitchdog @vercel i do use Cloudflare too, and i’ve got some projects hosted there. i’ve just never really hit Vercel’s free limits either, and for my frontend dev work Vercel still feels like the better fit: previews, DX, Next support, deploy flow, all that boring stuff that saves time. not anti-Cloudflare at all, just not fully convinced it replaces Vercel for that use case yet.

• 
  Brian Cardarella (@bcardarella) reported 25 minutes ago

  @mikehostetler I wouldn't build anything around what @flydotio offers, they just throw **** against the wall. Look at what @dillon_mulroy and his group over at Cloudflare are offering.

• 
  rchltmedia XPress! Tech Observer (@rchltXPSTech) reported 29 minutes ago

  can those retraded imbeciles at @Cloudflare/Chudflare make its captcha more reliable & efficient? if you can't make good captcha software, then you can **** off & burn your infra.

• 
  The Agentic Operator (@AgenticOperator) reported 30 minutes ago

  September 15. 52 days from now. Cloudflare changes its default AI crawler settings. If your site is on Cloudflare and you do nothing, AI might stop reading your pages. Training and agent crawlers get blocked by default on ad-supported pages. That includes ChatGPT's live fetch bot and Claude's real-time crawler. Here's the part that should scare you. Googlebot crawls for both Search and AI training in one bot. Block training crawlers and you might block Googlebot too. On accident. Because of a setting you never changed. Cloudflare's CEO confirmed this week that bot traffic has now passed human traffic on the internet. More machines read your site than people do. And in 52 days the biggest CDN on the planet changes who gets in by default. Check your Cloudflare dashboard. Security settings. AI crawler controls. If you haven't touched them, they're about to touch you. Most site owners don't know this deadline exists. The ones who miss it won't know they're invisible until the pipeline dries up months later.

• 
  Bulls & Barons (@BullsandBarons) reported 32 minutes ago

  Similar to @MEADGod and @ponsdotfamily, our opps (who know how bullish this is) submitted a completely unsubstantiated false report to @Cloudflare. It included no evidence or logs or anything. Unfortunately, Cloudflare acts on these reports immediately without reviewing them and then has a very long delay to appeal. The site is temporarily affected by this. An appeal is pending and if not answered soon, we will simply remove Cloudflare from the app entirely. To be certain, we reviewed the production code, player profiles, and available server logs and found no phishing content or credential collection whatsoever. The site never requests seed phrases or private keys and uses private wallets like any other app. Your wallets, tokens, and buildings are safe. An appeal has been submitted, and official updates will only come from this account. TLDR: Haters gonna hate.