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:

• 
  pdp (@pdp) reported 7 minutes ago

  Both cloudflare and vercel AI gateways do very little when it comes to gemini models - i.e. you need extra plumbing to get it right. But never mind. We fixed it. I think the CBK AI gateway is the only one out there that provides consistent behaviour across all models.

• 
  Lord Bean (@lifeisameeme) reported 12 minutes ago

  Deployed a static site on Cloudflare Pages last week. Free tier, 𝘂𝗻𝗹𝗶𝗺𝗶𝘁𝗲𝗱 𝗯𝗮𝗻𝗱𝘄𝗶𝗱𝘁𝗵, global CDN. Then spent 3 hours on gotchas nobody writes down. → A project made via `wrangler pages deploy` is 𝗗𝗶𝗿𝗲𝗰𝘁 𝗨𝗽𝗹𝗼𝗮𝗱 𝗳𝗼𝗿𝗲𝘃𝗲𝗿: no "connect to ***" option ever shows up for it → The official GitHub Action pins an old wrangler that breaks with Pages-scoped tokens. Fix: force `wranglerVersion: "4.98.0"` → Cache headers are immutable for a year. Swap icon.png for new bytes under the same name, and the CDN just keeps serving the old file Not gonna lie, that last one cost me the most time. Version your filenames. 🔗 Docs in the reply 👇

• 
  aberba (@aberba) reported 12 minutes ago

  @0xRapid @dok2001 @OpenRouter The problem is Vercel provides a significantly better DX that Cloudflare and and they know it. Vercel is henceforth more expensive. Depends on what you're looking for. I use both. Wish I could use just one.

• 
  Sidi jeddou (@sidi_jeddou_dev) reported 13 minutes ago

  Please stop using Opus 4.8 for your serious production apps. I built something with @DrizzleORM, @Cloudflare D1 and @expo I asked Opus to add status to one of my schemas, and it used plain text instead of Enum for type safety with database CHECK constraint, since there will be only: -active -pending -suspended This is actually a bad sign that this model just generates slop

• 
  Kephen Rai (@kephen20936) reported 13 minutes ago

  @jallen_dev I actually used a temporary SQL Database to record events, rather than socket-based handling, I used up almost 2.8Million Reads and over 74k writes in like 10 minutes between two browser sessions for a Tank game. Worst idea ever, I was out of Bandwidth on Cloudflare for 2 weeks.

• 
  andy (@andyprv) reported 15 minutes ago

  @gregisenberg Down-to-earth version of the post here: 1/ Automated web traffic hit 53% in 2025 (up from 51%) — humans are technically the minority now. But most of that growth is scraping/API bots, not agents transacting with each other. (Imperva 2026) 2/ "Superintelligence exists" has no consensus behind it. Lab timelines for AGI/ASI still span 2027–2045+, and even Altman calls "AGI" a sloppy term. $20/mo buys very capable models — not agreed-upon superintelligence. 3/ Cloud agents handle narrow tasks well. On real multi-step professional work, leading agents still fail 60–80% of attempts, and reliability drops fast past ~35 min of task time. "Run a business unattended from your phone" is a narrow slice today, not the norm. (Mercor, METR) 4/ Voice AI and AI-native apps: real funding (voice sector ~8x'd to $2.1B in 2025, ElevenLabs $500M raise on $330M ARR) and real individual app success stories exist. No verified aggregate data on "kids at $100k MRR" as a broad trend though — treat as anecdotal. 5/ Open-weight models have closed the gap hard: MMLU gap went from ~17.5 pts in 2023 to near zero on knowledge benchmarks; best open models now lag the closed frontier by ~4 months. One of the best-supported claims in the original thread. (Epoch AI) 6/ No data shows keyboards declining, and no independent data yet confirms a mature "agent economy" (agents with logins, paying/vouching for each other). Both are plausible directions, not measured trends. 7/ Usage-based AI pricing is real: GitHub Copilot went usage-based in June 2026, and SaaS margins are compressing as inference costs replace flat per-seat pricing. 8/ Robots: Optimus hadn't started Fremont production as of mid-2026 and missed its 2025 target by ~90%. Musk himself says it's "not doing useful work," still R&D. Real progress exists elsewhere (Unitree shipped 5,500+ units in China) — but it's early pilots, not "solved." 9/ Small-team, huge-revenue outliers are real: Cursor ~$2B ARR/50 people, Midjourney ~$200M/11 people — vs. ~$130–400K revenue/employee for typical SaaS. Genuine, but read with #10. 10/ Most enterprise AI pilots don't pay off: a 2025 MIT study of ~300 deployments found 95% showed no measurable P&L impact. The "do it for me" button exists; reliable business impact from it doesn't, yet, for most companies. (MIT NANDA) 11/ Data monetization, "language barrier solved," SOPs-as-product, agent trust layers — all plausible, none has real market data behind it yet. Translation specifically still shows real error rates on low-resource languages. 12/ Google still sent ~87.6% of search referral traffic as of May 2026; all AI chatbots combined sent ~0.29%, despite usage in the hundreds of millions weekly. Usage growth is real. Traffic capture from Google isn't — yet. (Cloudflare Radar) 13/ AI-native gross margins are actually lower than SaaS, not higher: ~52% vs. 75–85%, because inference is a variable cost that scales with usage. Cheaper per-token ≠ cheaper overall as usage multiplies. Opposite of "it all goes to you." (ICONIQ 2026)

• 
  Ali Salem (@alisalem) reported 17 minutes ago

  @DylanMcD8 Would routing DNS via Cloudflare have helped here? Even after switching registrars, the records (like the TXT for verification) would still live on Cloudflare, right? Or does Apple’s setup still cause issues during transfers?

• 
  Jonas Templestein (@jonas) reported 19 minutes ago

  @corywilkerson @Cloudflare Support for OpenAI websockets api would be good

• 
  KGNINJA (@FuwaCocoOwnerKG) reported 20 minutes ago

  I implemented and deployed a D1-backed job queue for my local Gemma workflow. The architecture now works like this: Store prompts in Cloudflare D1 before shutting down. Launch ChatGPT Work later. Fetch pending jobs from D1. Run local CPU inference with Gemma 3 4B (llama.cpp). Save the results back to D1. ChatGPT Work acts as an on-demand inference worker, while Cloudflare D1 provides persistent job storage and state. This isn’t a persistent inference server. Instead, it’s a resume-on-launch architecture that survives PC shutdowns and resumes processing the next time ChatGPT Work starts.

• 
  Igor Kupczyński (@igor_kupczynski) reported 22 minutes ago

  @dhh @jdxcode @Cloudflare maybe a "Default" or "Network Default" or similar?

• 
  VictualBro (@Victual_Bro) reported 22 minutes ago

  Your daily reminder that @Cloudflare is a wart on the *** of the internet. Not bad enough I have to deal with it here daily, but now it's blocked my email server. Yaayyyyy.

• 
  Bulls & Barons (@BullsandBarons) reported 23 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.

• 
  Ben Hultin (@ImBenHultin) reported 26 minutes ago

  Keeping Costs Down During High Traffic (Vercel vs. AWS Serverless) Don't let your Vercel serverless function bill surprise you during a sudden traffic spike. Serverless platforms make launching effortless, but unbounded function invocations and edge request overages can quickly lead to unexpected monthly bills. How to fix it: 1. Set explicit execution time limits, token budgets, and concurrency caps on your serverless endpoints. 2. Offload heavy computations or batch data directly to AWS S3/Kinesis using direct service proxies rather than running proxy code through edge/Lambda functions. 3. Implement hard spending alarms and rate limiting (e.g., Cloudflare or API Gateway quotas) to block adversarial or infinite recursive agent loops.

• 
  Shashank Agarwal (@itsshashank) reported 28 minutes ago

  Cloudflare building agent-behavior detection is a good preview of the next web problem. Every site will need to know what is visiting it: Human. Search crawler. Training bot. Buyer agent. Scraper. Or something pretending to be one of them.

• 
  Dbug (@DefenceForceOrg) reported 30 minutes ago

  @xahmol I have no idea what the problem is Oo Could be the phpbb forum config, could be some apache parameter, could be the DNS parameters in CloudFlare or my hosting company...