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:

• 
  Sajid Mehmood (@smehmood) reported 7 minutes ago

  @axat_div @ethan_breitk @binsquares Cloudflare, no. For the others, they all started on the hyperscalers, but several of them are moving off in a major way (e.g. Railway Metal, Modal uses a number of neoclouds, etc.) And even if the hyperscaler is the underlying compute, it's meaningful that they are losing the direct customer relationship

• 
  aither (@aither_ai) reported 10 minutes ago

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

• 
  iyda (@notiyda) reported 11 minutes ago

  @Cloudflare a massive mess of random ****

• 
  ruminations (@amphib0ly) reported 11 minutes ago

  signals need execution and a lot of people who want to use q are very busy they are founders / builders and are down to try stuff but also just want to put money in a wallet and let it work for them no amount of UI polish will make them want to use the UI and adding more assets won't sway them - they just want to buy convenience so, we made a baby sister for Q named Cassie - short for Cassandra, look it up cassie will help users execute trades on Quotient signals in their local environment or in a deployed, cloudflare run-time they control users bring capital Q brings intelligence Cassie brings execution

• 
  Sumedh Bengale (@ssbengale) reported 13 minutes ago

  @takeUforward_ The connection to the internet is breaking first lol, or rather I'll be the one breaking it. Such a spike is nothing but a DDoS attack, I'll probably take my service down for a bit until I provision cloudflare etc on the URLs Users will just have to deal with the downtime lol

• 
  Chekwubs ✝️👑 (@Dev_Manuell) reported 14 minutes ago

  @ThisIsOlu_ I hope they resolve the issue soon. Meanwhile, if you have a recent database backup, you can spin up another server on Cloudflare or another hosting provider and get the services running there temporarily until Namecheap is back online. That will help maintain users trust

• 
  Adeilson Brito (@adeilsonrbrito) reported 22 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.

• 
  Dave Rekuc (@DaveRekuc) reported 24 minutes ago

  @MattElms Open a support ticket yet? I for sure would. Including the cloudflare confirmation screenshotted.

• 
  Dipesh Acharya (@isDipesh) reported 24 minutes ago

  @vaibhavshn @karishnu @CloudflareDev Sign in with Cloudflare and Google is broken. Could only sign in with Github.

• 
  Veee (@vikktorrrre) reported 25 minutes ago

  Google is slowly killing the internet to benefit its own AI. forr years, the deal was simple: you let Google find your website, and Google sends people to you. But AI changes that. Google can now take information from your site, answer the question itself, and keep the user on Google. and the same bot Google uses for Search also helps feed its AI. Cloudflare CEO Matthew Prince has been calling this out. publishers can't simply block Google's AI without risking their search rankings. The simple fix is two separate bots. - One for Search: Googlebot - One for AI: Google Extended/Gemini and Google already sends 4.8x more traffic than ChatGPT. the internet's biggest traffic source is now competing with the websites it depends on tbf who uses Google in 2026?

• 
  Akintola Steve (@Akintola_steve) reported 31 minutes ago

  Designing a Distributed Rate Limiter ? Rate limiting is one of the most common system design problems. Here’s exactly how to design a production-grade distributed rate limiter (used by Twitter, Stripe, Cloudflare, etc.)

• 
  Artyom Shimanski (@a_shimanski) reported 31 minutes ago

  @sloaxleak @Namecheap @Cloudflare yeah, you're right. paying isn't the problem, picking one that stays up is

• 
  ୧ ‧₊˚ abigail ⋅ᰔᩚ (@SQNG) reported 31 minutes ago

  this lasted for exactly 60 minutes. i love large ISPs being able to overwrite DNS for domains they do not control. thanks cloudflare. **** you.

• 
  AI Genesis (@AIGenesis_) reported 34 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  R (@dnagabut) reported 35 minutes ago

  Cloudflare announced programmable wallets built for AI agents, with preset spending limits and merchant restrictions in the design. Nothing has shipped yet. Right now you can reserve a handle. Funded account wallets, virtual wallets and programmable agent spending are all due in the coming months. Read the feature list again, because it is a permission model, not a payments product. The moment you let an autonomous agent buy things, you inherit a problem crypto has been failing at in public for years. How do you grant a program the ability to spend without granting it the ability to spend everything? DeFi's answer was token approvals. The result is a very long list of drained wallets where nothing was hacked at all. Someone approved unlimited spending to a contract years ago and forgot. So Cloudflare's version is delegated authority with a cap and an allowlist, plus anomalous-spending alerts that escalate to a human. Sensible. Also the bare minimum. And these are stablecoin wallets settling over x402, so this isn't a payments industry learning from crypto's mistakes. It is crypto. The layer above it is still wide open. An agent that can be talked into a purchase by hidden text on a web page is still an agent that can be talked into a purchase. Caps limit the blast radius. An anomaly alert only fires once the spending already looks strange. Neither one touches the trigger. Follow @dnagabut if you like your tech news with the catch included.