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:

• 
  Ross (@402Signal) reported 7 minutes ago

  402 Signal Daily — Aug. 15 One real signal in the last 24h: @Cloudflare can now detect MCP traffic at the network layer and block agents that bypass approved MCP servers. That matters for x402 too. Paying for a tool is the easy part. Enterprises still need to know which agent called it, what data it sent, whether it was allowed, and how often. Machine payments are getting a security perimeter.

• 
  Javed (@jshai0) reported 10 minutes ago

  The final result: • 27.5M+ stored OHLCV rows • 122,960 Parquet objects • 13,154 chart artifacts • Cloudflare-native daily updates • A small API read path • No provider call for every chart request We stored the data because repeated API calls were the problem. We built the API on top of our own data because predictable reads were the goal.

• 
  Gregory (@_studable_) reported 12 minutes ago

  just got my cloudflare bill and it's over $17, so i will be hereby shutting down gexx

• 
  OldOne (@vale_wanderer) reported 17 minutes ago

  I hate @Cloudflare. Seriously obnoxious service that is an insult to anyone who values privacy and uses a VPN.

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

  Real audit finding. Changed the details, but the problem is exact. D2C brand. $3M revenue. Four problems found at the same time. Problem A: Cloudflare was blocking PerplexityBot. Invisible on one entire AI engine. Problem B: Hero product had no machine-readable price in schema. Disqualified from AI comparisons before it even had a chance. Problem C: 4,200 reviews were all sitting on their own site. AI treats them as one unverified source. Problem D: A competitor's comparison page was the #1 source AI cited about them. And it had the wrong specs. They had the budget for one fix this month. One. Which would you fix first? A, B, C, or D. There's a right answer. But it depends on something most people won't immediately think about. Reply with your pick. I'll explain why one of these is worth 10x the others if you fix it first...... and which one looks urgent but barely moves the needle.

• 
  Corey J. Gallon (@CoreyGallon) reported 17 minutes ago

  Personal apps break the cloud architecture we've spent 25 years building. That's the single point @KentonVarda makes in "Gadgets: Personal app vibe coding that is actually safe," on @aiDotEngineer's YouTube. Kenton is a Principal Engineer at Cloudflare and started the Workers project in 2017. The talk walks through a working platform he built to test the idea, and it's specific about the sandboxing that makes user-modified code safe to run. - The plugin-system death spiral. A developer drowning in one-off feature requests decides to rewrite around plugins, the rewrite never ships, and neither do the features. - The alternative is users editing their own copy. The developer ships a clean core app, and anyone who needs a feature asks an agent to add it, just for them. - Server-per-user is the blocker. One blessed version of an app running on your server is convenient for developers and makes customization impossible, which is exactly what today's vibe coding platforms are built on top of. - Gadgets work like documents, not deployments. Think Google Docs: hundreds of gadgets, each one an app with its own code, each one shareable. - Sharing lives in the platform, not the app. Because a gadget is a single shareable thing, access control is implemented underneath it, so the app can't get it wrong. - Blueprints are code without data. Export a gadget you like as a blueprint, and other people instantiate their own gadget from it. - The agent modifies the app, not just the content. Asked to build a slide deck, Claude added strikethrough, text centering, and an SVG paste box to the Slides app itself when the features it needed weren't there. - Security by containment, not by correct code. The client runs in a null-origin iframe sandbox under CSP that can only postMessage to the parent; the server runs in a dynamic worker sandbox. Neither can reach the outside world, so an XSS bug leaks nothing. - Cap'n Web RPC connects the two halves. The postMessage channel carries an RPC session through to the gadget's server code, written as a durable object. - No containers, no database. The whole thing runs on dynamic workers and durable objects, and the entire demo ran locally on his laptop on workerd, the open source Workers runtime. He also explains why the code isn't on GitHub yet, which he'd promised in the abstract. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!

• 
  Serge and Genetics (bio/acc) (@sergey_science) reported 21 minutes ago

  Tested @mastra agent on CloudFlare worker first, noticed slow responses, then tested same code on @Railway. 60% faster responses. But the speed wasn't even the reason - CF workers have too little memory to handle thousands of genetic variants in one go, they crashed. On Railway I can have 24Gb without breaking the bank. Railway won. Genetic researcher agent Diana has a new home now. FYI @JustJake

• 
  Adeilson Brito (@adeilsonrbrito) reported 24 minutes ago

  Cloudflare released one of the most consequential agent-security capabilities I've seen recently: its Gateway can now identify Model Context Protocol traffic at the network layer, surface previously invisible "shadow MCP" connections, distinguish direct MCP traffic from approved Portal-mediated traffic, and enforce policies that block MCP calls which bypass the governed route. There's an important architectural detail behind this. The new MCP 2026-07-28 specification exposes protocol and operation information directly in HTTP headers — "MCP-Protocol-Version", "Mcp-Method", and "Mcp-Name" — on every request, replacing the old connection-scoped handshake. Today, Gateway uses the protocol-version header to detect MCP traffic and enforce Portal-only routing at the network level. Cloudflare has indicated that tool-level policy — using "Mcp-Method" and "Mcp-Name" to govern individual tool calls — is coming next. Either way, the architectural shift is the same: infrastructure can increasingly identify, audit, and govern agent activity without depending on the agent itself to behave correctly. Cloudflare describes two distinct enterprise problems. Shadow MCP occurs when an employee connects an agent directly to an unapproved MCP server. Portal bypass happens when the server itself is approved but the user connects directly to it, skipping identity controls, DLP, curated tool catalogs, and tool-level audit trails. This is the key point: Agent security is beginning to look less like prompt security and more like Zero Trust. As agents become actors inside enterprise systems, security will increasingly depend not only on what we instruct agents to do, but on what the infrastructure allows them to do.

• 
  .null. (@Blacktrace_) reported 25 minutes ago

  @Cloudflare effectively putting the “bouncer” at the network layer rather than asking the agent to behave itself.

• 
  Joe Hansen (@joehansen) reported 25 minutes ago

  🚨 Cursor adds Firetiger team to close the loop from writing code to running it in production • The Firetiger team is joining Cursor • Firetiger builds AI agents that monitor software after it ships — watching rollouts, catching regressions, investigating incidents, and feeding findings back to coding agents • Founded in 2024 by Rustam Lalkaka and Achille Roussel (ex-Cloudflare, Twitch, Segment, Twilio) • Goal: agents that can ship a change, observe how it behaves in production, and fix problems when they appear • Firetiger’s work will be integrated across Cursor as part of a broader push toward long-running, context-aware agents This is the logical next step after SpaceX locked in full ownership of Cursor. Writing code is becoming cheap. Making sure that code actually works once it hits production is still expensive and manual. By absorbing a team that specializes in the production feedback loop, Cursor is trying to own the entire cycle - generate, deploy, observe, repair, inside one system. That is the difference between a coding assistant and an autonomous engineering layer.

• 
  Jon raRaRa (@jon_raRaRa) reported 26 minutes ago

  @rrespectorr @Cloudflare @fct_pt Damn not good! Wondering if I should make one for 2027 🤔

• 
  Mark Kilby (@MarkKilby2) reported 28 minutes ago

  Getting constant cloudflare errors when access your site, What's the solution @gameknot ?

• 
  Gibran Corbin (@Sendable_me) reported 30 minutes ago

  @launch_llama What "AI agent traffic" actually looks like when you measure it: Over ~1,000 requests to my site, 421 came from AI agents. 74 different ones. Every single one arrived as an IP address claiming to be a bot — no signature, no verifiable identity, nothing to bill against. The standards to fix this exist. Cloudflare, AWS and Coinbase all shipped them this year. The agents haven't caught up. npm i wayleave

• 
  Philippe Martin (@PhyByte) reported 31 minutes ago

  Writing the code was never the hard part. Owning what happens after it ships is. @cursor_ai bringing in a team that built agents specifically for that post-deploy loop (with real production experience from Cloudflare, Twitch, etc.) feels like one of the more grounded moves in this space with everything that happening at @SpaceXAI with @grok

• 
  hexmint ✌️ (@hexmint) reported 31 minutes ago

  @Cloudflare you really need to QA this Create Worker page. If I enter two letters in any of the text boxes here, the first letter is lost. And if there is a single letter there, I need to press backspace twice to delete it. Feels like a React issue idk