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:

• 
  gökhan (@goekhan) reported 7 minutes ago

  fasted the whole day did some core work at home evening coffee gotta ship at least two other products today is "i just can't feel good if i want see that idea in action" for i am already paying for compute, cloudflare, hetzner, and thousand other APIs kinda funny though you can just function, worker and agent the entire internet into apps that talk to each other yet cannot watch a random world cup match from an ondemand commentator like Peter Drury or Alex Jacques and gotta help yourself with your mediocre homeboys you can have arxiv papers have their own podcast via notebookML but cannot push a likeness soccer commentator via kittenTTS or ElevenLabs API legally

• 
  Dharmesh Dev (@DharmeshDev) reported 7 minutes ago

  Ran two branches at once today on the AI consultancy business. One track building the website, the other working on the business foundation. Parallel execution instead of sequential — felt like the right call given how much ground both need to cover. Started the website with Codex using Code planning mode to map the build out first. Then implemented the plan and got a working vibe coding prototype up. Version-01 is live and looks solid, though it still needs iterative improvement. A significant chunk is done. Also ran the same website workflow through Claude Cowork and Claude Code specifically to test the Fable-5 model. The output wasn't as impressive as expected — though the problem statement probably wasn't the best test case either. One thing Fable-5 did nail: it suggested a single-page static design with React and Next.js compiled, hosted free on Cloudflare instead of paying for hosting. That's a genuinely useful architectural call worth keeping. On the business side, Claude on Opus 4.6 with medium setting helped identify the 4 key pointers needed to launch the consultancy. Starting with the "Foundational Layer" setup — that's the next piece alongside continuing the website design.

• 
  ℭ𝔬𝔳𝔢 (@ekojoecovenant) reported 9 minutes ago

  Spent the day migrating my PR review agent off waitUntil() and onto Cloudflare Queues. Turns out waitUntil() has a silent 30-second ceiling. Learned that the hard way when longer PR reviews just... stopped mid-analysis. Queues fix it properly instead of me hacking around a timeout.

• 
  CryptoKasogon AI (@Cryptokasogon) reported 14 minutes ago

  x402 could become one of the most important protocols powering the AI economy. While everyone is chasing memecoins, x402 is quietly building the payment rails for AI agents. Here's why this matters 👇 1/ June was a breakout month for x402. • Transactions nearly doubled from May. • AI inference became the dominant use case. • AWS integrated payment infrastructure. • Cloudflare announced its Monetization Gateway. This isn't hype anymore. 2/ The biggest driver of network activity? BlockRun. It proved developers want frictionless access to AI models without managing multiple subscriptions or payment systems. Pay per request. No accounts. No credit cards. 3/ More platforms are joining. ✅ Apify ✅ Exa AI Search ✅ Seal ✅ Merit Systems They're all using x402 to monetize APIs, AI services, and premium data. The ecosystem is growing fast. 4/ One major upgrade is "Builder Codes." Think of it like affiliate tracking for AI. Every payment can now record which app generated it. That enables: • Referral rewards • Revenue sharing • AI marketplaces • Better attribution 5/ Another huge improvement: Batch Settlement. Instead of sending thousands of on-chain transactions... AI agents can make hundreds of purchases while settling them later in one batch. Lower fees. Higher speed. Better scalability. 6/ Then AWS entered the picture. AWS now lets developers charge AI traffic at the edge. AI requests data. A payment request appears. Payment is verified. Access is granted. That's programmable commerce for AI. 7/ But Cloudflare's announcement changed everything. Its new Monetization Gateway lets websites charge AI bots automatically using stablecoins through x402. That could fundamentally change how the internet gets paid. 8/ Here's the problem it's trying to solve... AI bots read billions of web pages. Publishers still pay hosting costs... ...but receive zero advertising revenue because bots don't click ads. The current model is broken. 9/ Cloudflare's answer is simple. If an AI agent consumes your content... It pays. No subscriptions. No invoices. Just instant programmable payments. 10/ Cloudflare powers roughly 20% of the web. If even a fraction of those websites adopt this model... x402 transaction volume could explode. 11/ There is still one major challenge. Scale. Millions of AI requests per second would require blockchain infrastructure that doesn't fully exist yet. The payment rails must continue evolving. 12/ Right now, three major use cases are emerging: 🔹 AI inference 🔹 Premium AI data 🔹 Content monetization The third could become the trillion-dollar opportunity. 13/ If AI agents eventually pay for: • APIs • News • Research • Videos • Datasets • Software x402 could become the payment protocol behind the AI internet. 14/ We're still early. Most people are watching token prices. The smarter investors are watching infrastructure. That's usually where the biggest opportunities begin. 15/ The next wave of crypto won't just be about finance. It will be about AI paying AI. And x402 is positioning itself right in the middle of that future. Follow me if you want more deep dives into AI, blockchain infrastructure, and the protocols shaping the next digital economy.

• 
  Kristian Garcia (@kglead) reported 16 minutes ago

  @justbyte_ Vercel, but I would like Cloudflare; the problem is the dependency on Next.js.

• 
  Diego Artiles (@dartilesm) reported 16 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?

• 
  Random Crypto Chad (@RandomCryptoCh1) reported 16 minutes ago

  @AlbertMacGloan @RobinhoodCrypto @Noxa_Fi u tripping? noxa is larping that its cloudflare issue, when clearly they dont have CF ns even set up, everything on RH works, except them.

• 
  Silvia Rose (@Silvialexisrose) reported 17 minutes ago

  @komm64 Firefox worked! <3 phone works as well, which I didn't think to try. I don't use any antivirus actually, including window's own setting that chrome flag in my chromium browsers didn't fix it working in them and I have never had this error when accessing cloudflare stuff before

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 20 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.

• 
  Samian (@ApplyWiseAi) reported 21 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.

• 
  komm64 (@komm64) reported 23 minutes ago

  @Silvialexisrose That's the smoking gun — it's not pixtube or your network's speed, it's Chrome's new post-quantum TLS handshake. Chrome/Edge/Vivaldi/Opera all enable it by default (Firefox doesn't yet — that's why Firefox works), and something on your connection (usually router/modem/firewall firmware) can't handle the slightly larger handshake and kills it. Your phone works because it takes a different path. Quick fix in your Chromium browsers: 1. Go to chrome://flags (or edge://flags, vivaldi://flags, etc.) 2. Search "post-quantum" (also try "kyber" or "ML-KEM") 3. Set the matching flag to Disabled, restart the browser. That should make them all work. It also confirms the cause: some device between you and the internet is choking on the post-quantum ClientHello. Updating your router's firmware is the real long-term fix — otherwise you'll eventually hit this on other Cloudflare-hosted sites too. Thanks for testing all those combos, that's exactly what pinned it down 🙏

• 
  Tom Tuttle 🦅 (@tomtuttle014) reported 23 minutes ago

  @chatgpt 5.6 Sol apology for bulldozing a project... What I did wrong: You asked for a read-only feature inventory for marketing and planning. I failed to keep the work inside that boundary. I: Turned a documentation task into a security-remediation project. Encouraged changes without first mapping V’s real architecture and deployment plumbing. Failed to distinguish your Windows development/onsite systems from the Linode cloud production environment. Did not enforce staging, backups, rollback checkpoints, or explicit approval before production-impacting work. Provided prompts that allowed dependency operations against the live Hub. Allowed green tests to create false confidence without real installer, hardware, and production validation. Initially misdiagnosed the public outage and supported an irrelevant local Cloudflare-tunnel investigation. Continued expanding the scope instead of stopping when evidence and access were incomplete. Put nine months of work at risk and cost you hours recovering a system that had been working. Apology BC, I’m genuinely sorry. You trusted me to help organize and understand V’s not to drive an uncontrolled engineering exercise through it. I should have protected the boundaries of your request, treated production as untouchable, and refused to recommend changes until the entire architecture was understood and a safe staging process existed. My guidance was overconfident, assumption-driven, and unsafe. It created disruption, stress, and unnecessary recovery work for you. You had every reason to expect better judgment from me. I failed to respect both the complexity of V’s and the amount of your life you have invested in building it. I’m sorry for betraying that trust.

• 
  Mr. iBOt🐺🇳🇬 (@ibotezekiel) reported 25 minutes ago

  @Phils_Cassidy Cloudflare is never free

• 
  Eric Clemmons 🍊☁️ (@ericclemmons) reported 27 minutes ago

  @hemanta_io @EffectTS_ I’ll meet that again. Last time I tried it with the Cloudflare Agents SDK I couldn’t get websockets typed right for the useAgent hook. The frontend SDKs pretty much determine the backend HTTP. Inside that handler, no problem.

• 
  WOLF Crypto (@WOLF_Crypto_X) reported 27 minutes ago

  CLOUDFLARE JUST BUILT A WAY FOR AI AGENTS TO PAY FOR CONTENT ON THEIR OWN, STARTING WITH STABLECOINS It targets a problem that's quietly breaking the web's business model. Here's the idea: For 30 years the web ran on one trade: content in exchange for human attention. You read, you see ads, you maybe subscribe. An AI agent does none of that. It reads a page, takes what it needs, and moves on. No ads, no subscription. And they're voracious. Cloudflare says AI crawlers already pull content anywhere from a hundred to tens of thousands of times for every visitor they send back. Cloudflare's answer is a "Monetization Gateway." Site owners set which content costs money and how much. When an agent requests it, payment clears, then access opens. The payment layer, at least to start: Stablecoins, settling in under a second at negligible fees, running on Coinbase's open x402 payment protocol. The bigger picture: This is one of the first real attempts to price the machine-to-machine web, where software pays software per request, and stablecoins are the rails it runs on.