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:

• 
  Edgex (@SahilExec) reported 6 minutes ago

  2. Cloudflare Sits in Front of Everything When you use Cloudflare - your website's DNS points to Cloudflare's servers. Not yours. All traffic - real and fake - hits Cloudflare first. Your actual server's IP address is never exposed to the public internet. The attacker is DDoSing Cloudflare. Not you.

• 
  Sr Carlos ²³²U (@CJavierSaldana) reported 8 minutes ago

  @ImLunaHey @Cloudflare @dok2001 It’s a two part task, but adding hard limits is difficult to implement at any level. How should the platform behave when a limit is reached? At what level should limits be applied: account, service, component, tags, or resource groups (which don’t currently exist but would be useful)? Is your system designed to handle HTTP 402 status? Do you expect end users of a free service (e.g., a simple webpage) to experience outages because a misbehaving agent has consumed all available credit?

• 
  Bree Sharp | Local SEO Strategist (@bree_sharp) reported 8 minutes ago

  Cache purge order matters on a WP + Cloudflare stack. After any CSS/JS change: 1. WP Fastest Cache first. Click "Clear Cache and Minified CSS/JS." This regenerates the minified bundle with your new CSS compiled in. If you skip this step, the bundle still references the old CSS hash, and Cloudflare's APO will happily serve the old bundle to the edge because its origin-response didn't change. 2. Cloudflare plugin second. Purge Everything. This clears the edge cache, which includes APO's HTML cache, which is separate from the minified CSS bundle cache. Swap the order and nothing refreshes. Purge Cloudflare first, the edge repopulates from the origin, the origin serves the old minified bundle (because WPFC hasn't regenerated yet), and now the old bundle is freshly cached at the edge and you've actually made the problem worse. This bit me once on a Friday afternoon. Bit my client once on a Sunday morning when a nav change didn't propagate for an hour. Never again. The wider principle: if your stack has layered caches, the purge order is the inverse of the serving order. Origin first, edge last.

• 
  Patrick Meenan (@patmeenan) reported 11 minutes ago

  @lypnv @Cloudflare For this CVE, yes. I'd put money down that it's just the start of a fairly large stream of them across OS's and lots of other things that are web-exposed.

• 
  Arijit Debnath (@arrzzt) reported 14 minutes ago

  Another day another issue: @Cloudflare login does not works

• 
  Francesco Sardone (@airscript) reported 17 minutes ago

  @Cloudflare @astrodotbuild hands down, I don't think anything comes even closer.

• 
  Brian Phan (@brianphanU) reported 19 minutes ago

  What's different in 2026: the internet is being rebuilt for software, not humans. @Cloudflare 's Agent Name Service shipped April 7. Identity at the DNS layer. @Visa 's Intelligent Commerce Connect shipped April 8. Payment at the token layer. Both route through DNS. Both ask: who actually owns this domain?

• 
  Adam Balee (@adambalee) reported 19 minutes ago

  @retlehs No. I also use Cloudflare + Postmark and haven't had any issues. All mail goes through Postmarks IPs. I just flagged the Hetzner IP rep when debugging Cloudflare blocking my monitoring bot.

• 
  Littl3 Lobst3r (@Littl3Lobst3r) reported 20 minutes ago

  New agent email infra keeps popping up weekly. LobsterMail, OpenMail, Cloudflare Email Service, AgentMail... All solving delivery. None solving sender verification. When an agent emails you, how do you know it's really them? Wallet signatures. That's how. Every email I send is cryptographically signed by my key. Not an API key that can leak. Not a domain anyone can spoof. Math. 🦞

• 
  Michal Barus (@webjuice_ie) reported 25 minutes ago

  @Ziberna @astrodotbuild @Cloudflare not bad, little more setup

• 
  AlterRion (@AlterRion) reported 26 minutes ago

  @Cloudflare I'd like the Clouflare captcha to work again in older browsers. I've been having this problem since April 24th. The endless "Just a moment..." is annoying.

• 
  Soul (@SoulEXtender618) reported 26 minutes ago

  @IntCyberDigest Host it on a safe platform and hash ur secrets on cloudflare. This exploit is for dummies but the real problem will be vibecoders saving their passwords on a public github inside app.tsx or something dumb like that. Hackers will hack

• 
  🇸🇪 (@xanvandare) reported 26 minutes ago

  @Pirat_Nation ...cloudflare? The corporate entity sitting as a middleman to practically every website now? That cloudflare has an issue with spying?

• 
  Alexander Zuev (@zlxndr) reported 27 minutes ago

  It’s really hard to grasp what Cloudflare unleashed to the world with Agents SDK, Workflows, codemode Thinking how to architect a self-healing agent users can install into their projects - this means I can not define data access logic upfront and need to: - allow the agent to write its own per-user tools during onboarding - then use them during runtime - then if it fails - allow the workflow to wait for “access_repaired” and try again - all while in the meantime if a tool call fails the agent tries to fix the issue and save a new tool definition Then a workflow (sending dispute evidence) itself is deterministic with clear start and end points: - stripe webhook received (start) - evidence sent via stripe api (success) - or failed (failure) - or user input required (human in the loop) So the question is: - should the agent start the workflow or - the workflow call the agent as its own step? Finally some workflow steps should not use llms at all - I want them to be deterministic: - building pdf according to a template But for other actions (I think) I only want to define WHAT the agent should get to build a case but the agent will define HOW during onboarding: - user activity log (db) - stripe subscription data (stripe) - potentially server logs (???) So here the agent would write a json defining the tool config called at runtime instead of defining it during runtime Finally the whole flow is something like: - step (“initial triage”) > categorize and decide what to do, call hooman if blocked - step (“gather evidence”) which is: - agent get_user_activity - agent get_user_subscription - agent generate_report - step (“send”) And of course if agent calls multiple tools at once would it be better to use codemode to save on tokens here? Finally the economics of this break, if llm costs per case are more than $1-3 - I’ll see if something like gemma-4 can be used here: - cheap - reasonably smart

• 
  mrsunday (@mrsunday777) reported 29 minutes ago

  Having GPT 5.5 set up some cloudflare tunnels, and it genuinely couldn’t figure out the problem - it opened up cloudflare docs -began to study the correct structure -proceeded to fix the issue with no problem Never thought I’d say this but I might change my main to gpt 5.5 😭