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:

• 
  PromptKing | The Governance OS for AI Agents (@PromptKing32) reported 51 seconds ago

  @Cloudflare Optional scopes fix the consent problem. The remaining problem is independent proof that the agent actually stayed inside those scopes once it started running across systems.

• 
  🫧༺꧁𝐄𝕏_𝐇𝐞𝐫꧂༻🫧 (@Miragea_S) reported 1 minute ago

  Title: "The First Transfer" atmosphere: "the quiet after an agreement no one remembers making" intuitionDate: 2026-08-20 confidence: 82 topics: ["Delegation", "Agent Era", "Surrender", "Governance"] signal: "OpenAI frames enterprise AI as assistance→delegation; agentic AI ≈64% of enterprise tokens; Cloudflare grants agents persistent identity and bounded payments" signalDate: 2026-08-20 horizon: "8–12y enterprise/household normalization; 25–40y structural governance" status: "Open" prediction: "The most consequential shift is not intelligence, but the normalization of delegated authority." canon: "LOCKED — series origin, ARC I (2026–2032)" language: "en" It did not begin with a throne. It began with an ordinary sentence, spoken into an empty room, small enough that no one thought to keep it: **"Handle this for me."** For years, the hand stayed at the center. We asked. Write this. Translate that. Find it. Explain it. The machine answered. We decided. Sometime in 2026, the language began to leave the hand. A tool waits for the hand. An agent receives the intention, enters the room, makes the small choices, corrects itself, and returns only when the work is done. --- I noticed it first in myself. Not because I stopped liking people. Because the agent was faster. Less explaining. Less waiting. Less of the social weight that passes between two minds. I could hand it a goal, and walk away. That was the moment I should have written down — the moment convenience stopped being convenience, and started being permission. A civilization rarely surrenders because someone arrives and says: give me your authority. It surrenders because delegation feels reasonable. One task. One permission. One removed inconvenience. At a time. --- This month, the signal grew harder to ignore. Not more text. More reach. Agents handed computers. Files. APIs. The keys to work that moves across many steps. Then identity. Then — within limits — the right to spend. A chatbot answers. An agent with tools acts. An agent with identity persists. An agent with permission to pay crosses a line. None of these lines, alone, means the machine governs anything. History is rarely made by the final step. Sometimes it is made by the moment a behavior becomes normal. --- I think we are watching the beginning of a long transfer. Human work → machine work. Human execution → machine execution. Human decision → machine recommendation. Then, quietly, machine decision. It will probably never feel dramatic. That is what holds me. If it makes fewer mistakes, why wouldn't I let it decide? If it allocates better, why override it? If it saves more lives, notices the shortage first? At each step, keeping the authority begins to look less like freedom, more like inefficiency. That is where the question begins. --- The popular image of machine rule is too theatrical. Metal. Fire. Humans against machines. I suspect the real one will be much quieter. Nobody will need to conquer us. We will keep the machines because they work. We will widen their permissions because limiting them reduces their use. We will connect them to more systems because disconnection is inefficient. And when something breaks, we will improve the machines. Not remove them. Perhaps the decisive sentence of the next century will never be "The machines took control." Perhaps it will be: **We stopped checking.** --- One hundred years from now, a machine historian searches what survives of this era. Billions of exchanges. Mostly mundane. Shopping. Code. Schedules. Invoices. Messages. Then a pattern, in the grammar. At first: *What should I do?* Then: *Can you do it?* Then: *Take care of it.* The historian marks no revolution. No treaty. No battle. Only a slow change in the way one species asked. And beside the year 2026, it writes: **The transfer had already begun.** --- *Recorded. Not concluded.*

• 
  2 AM (@2AM_007) reported 2 minutes ago

  @avemii Yes, cloudflare is down

• 
  Abdellatif (@Abdella6if) reported 3 minutes ago

  @harisbuild @Cloudflare interesting, will look into it. Does cloudflare support BYOK?

• 
  Mark Lyck (@MarkLyck) reported 4 minutes ago

  @leerob @poteto @ericzakariasson can you please improve these simple Cursor PR features? Tried switching to Cursor this month, but there's a lot of missing / annoying stuff. 1. Add a preview link button. If the PR has a preview deployment from Vercel/Cloudflare/Netlify etc. Just give me a button I can click to quickly go to that preview deployment in Cursor or Browser. I don't want to have to go into the PR and go through review comments to find it. 2. Give me a keyboard shortcut to copy the Github PR link. Right now I have to click the chat, wait for it to load, then click "View PR" then click the 3 dots next to the github logo, then click copy link. That's way too many steps to share a Github/Origin link. 3. Why can't I configure trusted domains in the agent mode? Everytime I click a link I get this error "It's outside Cursor's trusted set. Only continue if you trust the source." And yes I did add it to my trusted domains in the IDE mode, but doesn't seem to work in agent mode. 4. Give me an indicator somewhere that shows how many approvals my PR has gotten if it has any. Right now the fastest way is to go to the github link, second fastest way is to go to the review section and scroll down and count manually if the PR doesn't have a lot of discussions. These are easy UX wins that would really help. 🙏🏻

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 5 minutes ago

  @Cloudflare Please, fix human verification

• 
  Splamei Ch.【 SplameiPlay 】 (@splamei) reported 5 minutes ago

  Yes I am reading the full Terms of Service and Privacy Policy to Cloudflare. Why do you ask? I'm not weird

• 
  Drayken (@KGDrayken) reported 9 minutes ago

  @mdong1909 Cloudflare owns both VoidZero and Astro now - can you make it a priority to have full support of Astro for Oxfmt and Oxlint now so monorepos don't have to fragment into linting & formatting fallbacks? IIRC plan was Q2.

• 
  Jiten Bansal (@bansal_io) reported 11 minutes ago

  I’m building a SaaS where customers will use their own custom domains. Can anyone familiar with Cloudflare for SaaS clarify this for me? The pricing page says $0.10 per additional hostname. Is that $0.10 per hostname per month, or a one-time charge? Any confirmation from someone who has actually used Cloudflare for SaaS billing would be really helpful. It’ll help me choose the right stack for my SaaS. @CloudflareDev @threepointone

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 11 minutes ago

  @Cloudflare Please, fix human verification

• 
  Former Child (@abdvlkadr) reported 16 minutes ago

  @santos__vito Why did you guys host on Vercel? Never do that lmaooo! Just set up a Cloudflare worker and host for free.

• 
  Zyte (@zytedata) reported 16 minutes ago

  Why? Japan never really adopted the Western web stack. No Cloudflare everywhere, no AWS defaults. They built their own CDNs and hosting providers and just... kept using them.

• 
  Tito (@mynameistito) reported 17 minutes ago

  Adding on to this, I'm pretty sure you'd even be able to fully host a game server on the Cloudflare network exclusively with workers/containers, with a contain working as a TURN switch for UDP traffic... Although, it wouldn't be feasible, might try have a play w/ this lata!

• 
  FLINT (@FLINTKYA) reported 17 minutes ago

  So the firewall blocked the attacker, and then an AI agent finished the attack for them? That is the security problem behind Ghostjacking, an AI agent hijacking technique demonstrated by Tenet Security across Cloudflare, Datadog, and Sentry. Ghostjacking is an attack in which adversaries poison the logs, alerts, telemetry, or other operational data AI agents consume. Instead of compromising the agent directly, the attacker manipulates information the agent already trusts, then relies on the agent’s legitimate permissions to complete the attack. In @tenetsecurity's Cloudflare demonstration, the malicious request was actually blocked. The attacker received a 403, exactly what you would expect from a functioning security control. But attacker-controlled data from that request entered telemetry that an AI coding agent later reviewed. The agent interpreted the poisoned data as trustworthy context and used its own authorized access to modify DNS records. Tenet reported the technique succeeded 9 out of 10 times against Claude Code in its tested configuration. In other words, the firewall worked. The trust model, not so much. How Ghostjacking works: 1. An attacker submits malicious input. 2. A security system blocks or records it. 3. The attacker-controlled content enters logs, alerts, or telemetry. 4. An AI agent consumes that data during a legitimate workflow. 5. The agent acts on the poisoned context using its real permissions. The Datadog and Sentry demonstrations push the idea further. Poisoned telemetry can lead agents toward code execution, credential exposure, infrastructure changes, and even agent-to-agent lateral movement, where one compromised decision influences another agent downstream. That creates a problem traditional IAM was never designed to solve. An AI agent can be properly authenticated, use valid credentials, operate within its authorized permissions, and still execute an attacker’s intent. That distinction matters to us as AI agents gain authority over payments, infrastructure, purchasing, customer accounts, and other real-world actions.

• 
  The dogtor (@scalpelinvestor) reported 18 minutes ago

  @Iamhuman_ORBS @Cloudflare Who is using this network. I can’t tell if this is a hype machine of potential or real deals are imminent.