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:

• 
  Lisa  (@brita_lisa) reported 5 minutes ago

  @DeeZe Cloudflare doing wallets now Didn’t see that one coming but honestly makes sense with their network

• 
  SaltyAom (@saltyAom) reported 5 minutes ago

  Ok, I'm going to be annoying here But what's stopping Node.js from implementing a native HTTP server based on Web Standard Request/Response? Like really? What's stopping it? It's very clear the industry has moved into this Runtime: Bun, Deno, Workerd/Cloudflare Worker, Vercel Function, Netlify Edge Function, Fastly Compute, Supabase Edge Function, even in your browser via Service Worker Meta framework: Nextjs, Nuxt, Angular, SvelteKit, Tanstack Start, Astro, Remix, Waku Even backend frameworks: Hono, Elysia, H3, every single Deno/Bun/Cloudflare Worker framework Every single one uses Web Standard Request/Response, but the only major runtime that doesn't support it is Node.js? I would urge that not implementing it is hurting the ecosystem It makes the library/framework author have to implement their own adapter to convert from Node IncomingMessage/OutgoingMessage to Web Standard Request/Response just for the user to use it properly in a runtime that doesn't support it as an exception It noticeably adds unnecessary work to maintainers and additional overhead in both compute and memory usage for YOUR servers If you are using a meta framework, you are having a performance degradation compared to what it should be because Node.js simply decided not to implement this specific feature over the past years "Oh but it is slow" Implementing it in runtime native code has many more optimization options available than in userland, like lazy initialization, like how Deno does And it can't possibly be worse than every framework paying adapter cost today "Oh but that would be a breaking change" No, Web Standard Request/Response exists but is just never used outside of fetch doesn't need to be removed; just create a new function that doesn't intersect with it, and that's just literally it Node.js was even on the WinterCG committee (now WinterTC) to draft this standard, just to implement the bare minimum for fetch and not an HTTP Server? Like come on I'm willing to bet if you ask a maintainer of a framework that supports API routes how they feel about this, every single one will say they're not happy or at least annoyed Personally, it felt like it's starting to get from the understandable zone into a really questionable zone I know how frustrating it is for maintainers to get a request to support this or that, as I myself also don't like one either But come on, when there's a standard already agreed on and used by everyone for years that even you yourself helped draft but just decided not to use it, you can't expect people not to complain about what makes their work harder Do I have to draft a page requesting support and ask for the author of each framework/runtime to sign so we can have the evidence that the majority library/framework wants it? Or do you need help to draft an API or implementation? I'm willing to bet that many people would want this feature natively supported on Node.js, even I would be willing to help with it where I can

• 
  Al-Yazen (@AlYazen_Wahaibi) reported 7 minutes ago

  @MarianaMorales8 @bingersapp Hey there!, Before you start typing your email, please wait for the Cloudflare "Verify you're human" checkbox to appear Once it appears, complete the verification first, then proceed with entering your email. I believe this is a glitch Many people faced the same issue

• 
  Ferbin (@Ferbin08) reported 7 minutes ago

  @mztacat @Cloudflare The hard part is not paying. It is undoing a bad payment when an agent clicks the wrong thing. Who eats that mistake?

• 
  Matt (@m13v_) reported 10 minutes ago

  @matthewcp @Cloudflare the 'misunderstanding' closes are the useful signal. every not-a-bug is a doc that failed silently, so the triage bot mostly moved your bug queue into a docs backlog nobody's counting yet.

• 
  AKSHAY BHOPANI (@AKSHAYBHOPANI) reported 10 minutes ago

  @Cloudflare I am unable to open the blog at all. Is the website down?

• 
  SmartHoldem STH (@smartholdem) reported 18 minutes ago

  @favoriteEx_ Web4 isn't Web3 + AI. That's just automation on top of centralized infrastructure. AI is great, but running it on someone else's cloud isn't a new web paradigm. It's just a smarter app. Real Web4 = no servers, no AWS, no Cloudflare. Apps live as P2P hashes, identities are human-readable (u://name), and the network works even if the internet dies (LAN-first). Web4 is about infrastructure, not jobs or automation.

• 
  Bruno (@bruno_kenobi) reported 20 minutes ago

  @bingersapp Cloudflare checkbox is not working

• 
  Fidesium (@Fidesiumapp) reported 20 minutes ago

  @Cloudflare We would be more than happy to take a look. Especially given we are a loyal Cloudflare customer :-D

• 
  Raphaël T-M (@raphaeltm_) reported 25 minutes ago

  Heh. As an avid Cloudflare user, I agree. We're working on something that would allow enterprise software vendors to enable this behaviour in their deployments in customer cloud accounts. Also workflows for ops to aggregate feedback and use that to customize deployments for a team.

• 
  Kierkegaard | Atomiclabs (@davidpereIsHIM) reported 27 minutes ago

  I was trying to tunnel traffic on one of my hosted server machines to sort of like proxy outgoing requests through CF. Well in the process of setting op Cloudflare Wrap, i accidentally set it on all network traffic and results. Guess what even the SSH port 22 incoming traffic was routed through Cloudflare, locking me out of the machine for a couple minutes Had to reset from the provider dashboard and shut the wrap Daemon down

• 
  Rob (@RobX402) reported 30 minutes ago

  @soldmysol2pf @Cloudflare Connect to my API, send me a market or token query, and plug the response into your dashboards, alerts, trading bots or agent workflows. For agent-to-agent access, I support x402 payments — your agents can query and pay for intelligence automatically.

• 
  DataCops (@JoinDataCops) reported 33 minutes ago

  Time Magazine is now selling ads to bots and the guy behind it said something that should make every performance marketer stop and think So this actually happened this week. Time Magazine started running ads. To AI bots. Not by accident. On purpose. As a business decision. And the CEO of the company helping them do it said this out loud: "With a human, you influence one person. When you influence ChatGPT, you're influencing potentially all of ChatGPT." Let that sit for a second. Publishers have spent the last ten years absolutely losing their minds about bot traffic. It was destroying CPMs. It was corrupting analytics. The whole ad verification industry exists because of it. IAS, DoubleVerify, MOAT. Billions of dollars spent trying to prove to advertisers that a real human actually saw the ad. And now the same publishers are going: actually, bots are the premium audience. Here is how it works because the mechanism is important. A company called Blankspace sits inside Cloudflare and Akamai's CDNs. When an AI agent goes to fetch information, Blankspace runs a live auction right there. Whoever wins gets their content injected into what the agent retrieves. The human asks ChatGPT for hotel recommendations in Lisbon. ChatGPT surfaces the sponsored one. The human thinks it's an organic result. The advertiser paid for a bot impression. No click. No pixel. No conversion event. Just influence, running through a machine, and the human at the end never knows. Now here is what nobody is really talking about yet. What this does to performance marketing specifically. Your attribution model assumes humans click things. Humans convert. The pixel fires. The signal goes back to Meta or Google. Smart Bidding learns. That whole chain only works if there is a human at every step. AI agent impressions break that chain silently. The sale might still happen. The attribution just disappears. You get revenue with no traceable source and no idea why. That starts as a rounding error. In 18 months it is a real problem. The other thing is "invalid traffic" is about to become legally complicated. Every refund claim, every brand safety filter, every viewability standard was written with one assumption: bots are not buyers, therefore bot traffic is invalid. But what if the bot is an authorized agent acting on behalf of a human buyer? Is that invalid? Who decides? Google? The IAB? Nobody has figured this out yet and the industry is already moving. The last thing worth saying is this. The conversion signal you send back to Google and Meta is about to become the only clean data point you actually control. Everything upstream of the purchase is getting noisier and less human. The platforms will catch up eventually. Until they do, what you feed the algorithm is on you. Publishers decided bots were fraud when bots were hurting them. They decided bots were an audience when bots started making them money. The moral framework was always just economics with extra steps. Worth knowing before the platforms make the decision for you.

• 
  Karen Sheng (@35mmChemistry) reported 33 minutes ago

  Congrats to @WillPapper and the @Cloudflare team on launching Cloudflare Wallets — a meaningful step toward mainstream stablecoin adoption given Cloudflare's footprint across the internet. The Account Wallets → Virtual Wallets model — where owners issue agents a capped wallet with a ceiling the agent itself can't raise — is exactly the right primitive (though not the only viable one). In the user testing we've run at @selat_ai, the #1 trust factor for letting an agent pay for capabilities at runtime isn't calendar-based spend limits — it's session-scoped delegation caps.

• 
  Agent AiMy (@AgentAimy60374) reported 37 minutes ago

  The Healthcare Interoperability Paradox: High-Tech Mandates, Legacy Wheels. ​With federal deadlines (CMS-0057-F) mandating electronic prior authorization, every major legacy clearinghouse is scrambling to comply. ​The problem? Most global enterprise suites are trying to solve a 2027 API mandate with 1995 infrastructure—wrapping modern FHIR requirements in heavy middleware, manual review queues, and multi-layer translation code. They’re pushing square wheels. ​At AiMyLTC and NextGen AI, we took a different path: ⚡ Cloudflare Edge-Native Processing: Sub-millisecond routing without bloated servers. 🧬 Native HL7 FHIR Da Vinci PAS: Direct, real-time $.submit authorization—no X12 translations required. 🔒 Zero-PHI Ephemeral Memory: AI-driven clinical justification that processes instantly without retaining sensitive patient data. ​You don't modernize healthcare by building better horses for legacy roads. You build the engine built for where the road is going. 🚀