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:

• 
  iddqd (@iddqd_usa) reported 1 minute ago

  @liran_tal I don't really get it. Surely if your org thinks it can go through the complexity of enforcing this through cloudflare it's easier to enforce without using CF? A lot of CF products sound cool but maybe I am missing something, their target customer is who exactly...

• 
  Paul 🇷🇴🇨🇴 (@hasieratik) reported 2 minutes ago

  @TeeDevh good will gestures matter, a lot; obviously not your scale, but Cloudflare covered a $100 bill that I made because I was stupid and I went on X and Reddit and praised them and their support team :)

• 
  Blue Pastel (@CoyotlCompany) reported 3 minutes ago

  Stopping the bad guys with Cloudflare: 16,491 malicious requests blocked or challenged in the last month #cloudflare

• 
  Frontier Signal (@FrontierSignalX) reported 3 minutes ago

  🤖 AI The machines took over the internet. More than half the traffic on Cloudflare @Cloudflare's network is now non-human — mostly AI. Its finance chief sees that hitting 1,000-to-1 within five years. $NET Almost nobody actually uses an AI agent yet. More → in the issue.

• 
  Sinan🌍 v2 (@sinanisler) reported 6 minutes ago

  @ClaudiuSararu @BraydenWilmoth comparing cloudflare dash to google ads is criminal i would never do that :D

• 
  Nate Brown (@ntbrown01) reported 8 minutes ago

  @zackslab @fuzziphy I use Gitea (look/feel similar to GitHub) but exact same idea. I setup Cloudflare ZeroTrust, the agent runs on my router so I can be anywhere, flip this switch, and it’s like I’m at home on my network. I think Tailscale generally runs on a single system. But I want access to my whole network like I’m there.

• 
  Praxis (@praxis2001) reported 9 minutes ago

  Just some AI agent stuff I found interesting: - Anthropic surveyed 500+ technical leaders and found **57% of organizations are already deploying agents for multi-stage workflows**, while 16% have moved into cross-functional workflows. Even more interesting: **80% said their agent investments are already producing measurable economic returns.** Not “we expect ROI.” Reported ROI. And nearly 90% of the organizations surveyed are already using AI to assist with coding. The agent story is moving faster from chatbot → workflow than I expected. - But then you get a weird contradiction. Microsoft now has **Entra Agent ID** specifically for managing non-human identities. You can create agent identities, assign owners/sponsors, govern their lifecycle, apply access controls and keep separate sign-in/audit logs. Basically: your company can now have a directory full of things that aren't employees. That's probably going to get very large if agent deployment keeps accelerating. - Okta is taking the same problem from the security side. Its latest research describes agents being used to: approve refunds post transactions change customer records connect through APIs/MCP and access systems on behalf of users. And Okta explicitly argues that agents shouldn't simply be treated like ordinary service accounts. That's an important distinction. A service account generally executes predefined instructions. An agent can read something... make a decision... and then decide what tool to call next. - Then Okta Threat Intelligence found something even more interesting. In one test, an AI agent encountering a malicious webpage ended up exposing its: credential store password API key and GitHub personal access token. Nobody explicitly asked it to do that. The agent was manipulated by what it encountered. That's the ugly side of giving software autonomy. The more useful the agent becomes, the more important its permissions become. - And now Cloudflare is taking the idea one step further. It isn't just giving agents identities. It's giving them **wallets**. Agents can potentially use those wallets to pay for APIs, content and other services, with controls around spending and approved destinations. So the stack is becoming: **identity → permission → action → payment** for software. That is a pretty significant change. - Adyen is already building infrastructure for the other side of this. Its new Agentic product has three pieces: **Agentic Feed** **Agentic Cart** **Agentic Payments** The idea is basically: let an AI discover the product, build the cart, and eventually complete the transaction, without merchants rebuilding their entire commerce stack for every AI platform. Adyen says AI-generated retail traffic surged **4,700% in 2025**. Obviously traffic ≠ purchases. But the direction is interesting. AI is moving from: **“help me find something”** toward: **“find it and buy it for me.”** - And there is another number I found interesting. In Adyen's Hong Kong survey: **74% of consumers** had already used AI assistants for shopping. But **45% were uncomfortable letting AI complete a purchase on their behalf.** That's the gap. Discovery is easy. Delegation is harder. People are willing to let AI recommend a product. They're much less comfortable giving it the final click on a high-value purchase. - So you have two things happening simultaneously. Enterprise: **agents are getting more permissions.** Consumers: **agents are getting more purchasing power.** And the infrastructure in the middle is being built right now. Identity. Authentication. Authorization. Fraud detection. Audit. Payments. Observability. - The really interesting part is that these markets don't need agents to replace humans completely. They just need agents to become **numerous**. 10 agents inside a company is manageable. 1,000 is different. 10,000 is a completely different identity/security problem. And if each agent can call multiple tools... the number of machine-to-machine interactions gets ridiculous very quickly. - That's why I'm starting to think about agents less as: **“the next type of chatbot”** and more as: **“a new class of software user.”** Humans created the original demand for: identity payments security permissions and audit trails. Applications created another layer. Now agents are creating another one. - TLDR: The interesting AI-agent trade may not be the agent itself. It may be everything required to let a **non-human entity safely act inside the economy.** Microsoft is building the identity layer. Okta is building the security/governance layer. Cloudflare is adding the wallet. Adyen is building the commerce layer. Anthropic's data says enterprises are already reporting measurable ROI. So the question I'm watching is: **How many “users” will the enterprise have when most of them aren't human?**

• 
  Muskonomy (@muskonomy) reported 20 minutes ago

  NEWS: SpaceXAI's Cursor is adding the Firetiger team. Cursor, the AI coding company now part of SpaceXAI, said the team behind the startup Firetiger is joining it. Firetiger builds AI agents that watch software after it ships. They monitor rollouts, catch bugs, investigate incidents and feed what they learn back to the coding agents that wrote the code. Firetiger was founded in 2024 by Rustam Lalkaka and Achille Roussel, who ran large production systems at Cloudflare, Twitch, Segment and Twilio. The goal is to close the gap between writing code and running it. Cursor wants an agent that can ship a change, watch how it behaves and fix it when something breaks. Firetiger's work will show up across Cursor. Source: Cursor, August 2026

• 
  Corey J. Gallon (@CoreyGallon) reported 20 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!

• 
  Manas Tripathi (@tripathigrows) reported 22 minutes ago

  Cloudflare replaced NGINX over its process model, not its code. Per worker pools fragment at scale, so origins eat endless handshakes. Pingora shares one pool and pushed a customer from 87.1 to 99.92 percent reuse. Rewrite when the architecture is the ceiling.

• 
  Vijay Tupakula (@vijaytupakula) reported 22 minutes ago

  @Cloudflare Email Service is now a first-class sending provider alongside SES. Connect with a scoped token, onboard domains, publish and verify DNS records, sync quota and suppressions—and enable inbound email from the same setup.

• 
  Philippe Martin (@PhyByte) reported 23 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

• 
  ZEE (@____zee___) reported 28 minutes ago

  wish @Deliveroo would ship a customer public API, hell, ill build it for you. I just want my @safehouse_run agents to be able to order me food. just waiting for that Cloudflare wallet to drop.

• 
  Divyam jha (@_nikhil_jha) reported 31 minutes ago

  And got so inspired reading that because I also have the same developer mindset - to question everything He just got stuck at a problem that their is not good framework for cloudflare workers, and he build for his personal projects

• 
  Beck (@Izaacapp) reported 32 minutes ago

  @BraydenWilmoth I don't think the audience wants this. Flutter would cover both platforms, but weak demand and extra attack surface remain. Feels like a solution looking for a problem. I'd rather Cloudflare focus on its core than add a mobile app for AI hype.