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:

• 
  Adrian Fritz (@adrianwjfritz) reported 2 minutes ago

  5/ Governments and major tech companies are already moving. Most blockchains are catching up. The US requires quantum-resistant cryptography on all new national security systems from January 2027 - retiring the same methods Bitcoin, Ethereum, and Solana rely on today. Cloudflare, Apple, Signal, Microsoft, and AWS are already deploying upgrades. 24 of the top 26 blockchain protocols still rely entirely on methods being phased out elsewhere.

• 
  Star Jessei💕 (@Starjessei_web3) reported 3 minutes ago

  What if your next customer isn't a person? AI agents are already buying compute, APIs, and services autonomously and @WalletConnect & @base Pay just built the rails for it. Here's what's actually happening onchain right now: ➫ Stablecoins cleared $46T in 2025 and for context, that's more than Visa moved all year. ➫ Base is holding $4.7B in stablecoin supply and pushed $2.5B plus through WalletConnect Pay in Q1 2026 alone. ➫ x402 lets AI agents hit an endpoint, get a payment request, sign a USDC micropayment, and keep moving. No unnecessary back and forth And it's not some niche crypto experiment because, Google, Microsoft, AWS, Visa, Mastercard, Shopify, and Cloudflare are all behind it. Additionally, Ingenico, the company powering payment terminals in 32 countries, has already integrated WalletConnect Pay. This is reaching physical retail now. WalletConnect Pay is the underlying wallet layer. 500M users. 700+ wallets. One integration. Commerce is going onchain and Base is where it's landing. It doesn't matter if the buyer is a person tapping their phone or an agent finishing a task at machine speed, WalletConnect Pay is how they connect to it. This is the future!!!!

• 
  BornToLose💀🍀🏆 (@__BornToLose__) reported 4 minutes ago

  Spectrum can bite my ***, wdym 30mbps down is fine? Was really hoping it was just a cloudflare thing or something on my end but nope, I'm genuinely just stuck with the world's shittiest ISP and nothing I can do about it.

• 
  Pivi (@ApplyWiseAi) reported 7 minutes ago

  grok just launched a plugin marketplace for building from your terminal mongodb, vercel, sentry, cloudflare, chrome devtools all pluggable. so your agent can ship to ****, check errors, and debug the browser without you leaving the cli this is the missing piece for

• 
  TheLarioso (@TheLarioso) reported 11 minutes ago

  @brivael You have these massive scripts CloudFlare many are connected to and collect ip:s and check if bots etc. - you could very well just go ip and block those that exist - yes, quite a few but can be done I think You do not need to go to a particular service, you vpn service has an ip.

• 
  Frank Karro (@imfrankkarro) reported 11 minutes ago

  So I stopped doubting and started building. Then hit a wall: a Cloudflare billing bug killed my infra setup. 3 hours convinced I'd broken something. Turned out to be an incident on their end.

• 
  Prince mendiratta (@PriMendiratta) reported 13 minutes ago

  @threepointone Relevant to this! We hit "other side closed" errors with buffered LLM calls (stream: false). Root cause: Cloudflare egress kills TCP connections idle for ~300s. Buffered calls keep the socket silent until done, so long generations get killed mid-flight. TCP keepalives don't help, only real data resets the timer. For large AI tool calls this can hit 10+ mins. Does your resumable buffer approach handle this?

• 
  Victor (@echo_vick) reported 14 minutes ago

  I can’t seem to access CloudFlare using my MTN network, but it immediately opens once I switch to Airtel. Does this happen to anyone else?, is this common?

• 
  Martin Stepanek 🏳️‍🌈 (@techseovitals) reported 15 minutes ago

  🟣 Underrated #TechSEO Tip GPTBot, ClaudeBot, and PerplexityBot all respect robots.txt. Block them and your content never appears in AI answers. Worth flagging that Perplexity's compliance has been disputed – Cloudflare found evidence they used undeclared crawlers to bypass robots.txt. I see site owners block these crawlers without realizing they killed an entire traffic channel. Check your robots.txt right now. Look for blanket `Disallow: /` rules targeting AI user agents. You might be invisible in AI search and not even know it.

• 
  dukeo (@dukeo) reported 27 minutes ago

  @EddCoates Had the same issue on one of our sites receiving millions of hits from scrapers while getting just a few thousands legit visitors per day. The only way is to be extremely aggressive in your Cloudflare setup.

• 
  Andrej Ruckij (@ruckiand) reported 32 minutes ago

  Online stores are panicking that AI bots are crawling their site and "stealing" their catalog. So they hit the one-click Cloudflare toggle and block everything. Most are solving the wrong problem — and quietly hurting themselves. 🧵

• 
  Vedant Anand 🐲/acc (@Vedantsx) reported 32 minutes ago

  @eastdakota @QuinnyPig @eastdakota please fix opennext for cloudflare 🙏🙏 I've tried to inform everywhere, for me shifting from Vercel to Cloudflare through opennext took a lot of pain

• 
  Nikhil Agarwal (@nikhildp) reported 36 minutes ago

  @ade_oshineye Won't it be better to fix the obvious billing issue first so that startups can use cloudflare peacefully? How can there be no limit on expense? Company should not have bear insane expense because of a dev mistake which causes dynamic workflow to go in infinite loop.

• 
  Puneet Patwari (@system_monarch) reported 37 minutes ago

  Tweet 3/5 Picking the algorithm is half the decision. The other half is: where do you enforce the limit? Most teams slap rate limiting at the API gateway and call it done. That's one layer. Production systems need at least two. Here's why. Layer 1: API Gateway (the front door) This is your first line of defense. Every request passes through here. Set global rate limits: "no client can exceed 1000 requests per minute." This catches: - Runaway scripts - Misconfigured clients - Basic abuse - Your own batch jobs (ask me how I know) Tools: Kong, NGINX, AWS API Gateway, Cloudflare. All have rate limiting built in. Layer 2: Per-service limits (noisy neighbour protection) You have 10 microservices. Your search service can handle 5000 rps. Your export service can handle 50. Without per-service limits, one client hammering /export at 200 rps takes that service down. And because /export is down, health checks fail, the circuit breaker trips, and suddenly other things start breaking too. Per-service rate limits prevent one endpoint from eating the capacity of another. Layer 3: Per-user limits (fair usage) One user is making 10,000 API calls per minute. Every other user is making 50. Without per-user limits, that one power user is consuming 99% of your capacity. Per-user limits: "each API key gets 100 requests per minute." Fair. Predictable. No single user can starve everyone else. This is also where you differentiate pricing tiers. Free tier: 100 rpm. Pro: 1000 rpm. Enterprise: 10,000 rpm. Rate limiting is literally your pricing enforcement. Layer 4: Per-endpoint limits (not all endpoints are equal) Your /search endpoint can handle 10,000 rps. It's fast, cached, lightweight. Your /generate-report endpoint does a 30-second database aggregation. It can handle maybe 10 concurrent requests before the database starts crying. Same global rate limit for both? That's a disaster waiting to happen. The heavy endpoints need tighter limits. The rule: at minimum, use two layers. Gateway-level for global protection. Per-endpoint or per-user for granular control.

• 
  ∱ (@Fallibilist) reported 37 minutes ago

  @ni5arga Yeah, not working on network DNS, cloudflare works