Cloudflare Outage Map
The map below depicts the most recent cities worldwide where Cloudflare users have reported problems and outages. If you are having an issue with Cloudflare, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Cloudflare users affected:
Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Bengaluru, KA | 1 |
| Montataire, Hauts-de-France | 1 |
| London, England | 1 |
| Greater Noida, UP | 1 |
| Attleborough, England | 1 |
| Colima, COL | 1 |
| Leuven, Flanders | 1 |
| New Delhi, NCT | 2 |
| Mâcon, Bourgogne-Franche-Comté | 1 |
| Amsterdam, nh | 1 |
| Ashburn, VA | 1 |
| Rosario, SF | 1 |
| Merlo, BA | 1 |
| Frankfurt am Main, Hesse | 1 |
| Birmingham, AL | 1 |
| Dayton, OH | 1 |
| Miami, FL | 1 |
| Osnabrück, Lower Saxony | 1 |
| Noida, UP | 1 |
| Bulandshahr, UP | 1 |
| A Coruña, Galicia | 1 |
| Easton, PA | 2 |
| Guayaquil, Guayas | 1 |
| El Port de Sagunt, Valencia | 1 |
| Medellín, Antioquia | 2 |
| Padova, Veneto | 1 |
| Farnham, England | 1 |
| Goiânia, GO | 1 |
| Zürich, ZH | 1 |
| Ulm, Baden-Württemberg | 1 |
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:
-
Anandu S (@byAnanduS) reportedCloudflare website seems very slow to load. Anyone experiencing the same?
-
NickelodeonLover (@DanielO04532942) reported@Cloudflare Just fix the error 521 already so I can go on HiMovies again.
-
Shreya (@Oblivious9021) reportedCloudflare took down 20% of the internet in 2019 with one bad regex. One Regex. How do you design systems that don't let a single human mistake cause global chaos?
-
bnou (@cyeux) reported@ThePooN @Cloudflare tell me if u fix it
-
Chieh Ger (@jay_kuro) reported@VFSGlobal I am trying to signup on the website but getting 401 on the cloudflare bot check. Where can I log my issue? I urgently need to renew my passport. I am based in Netherlands
-
czverse (@czverse) reportedThe number of qubits needed to break Bitcoin just dropped from 20 million to under 100,000. In 7 years. Cloudflare moved their post-quantum deadline up to 2029. Bas Westerbaan called it "a real shock." Most crypto holders haven't internalized what this means: every Bitcoin in a reused address is potentially harvest-now-decrypt-later vulnerable. The encryption isn't broken yet. The data being stolen today might not be safe in 2030. The migration is real. The timeline is closer than it was. The chains that move fast survive. The ones that don't will fragment. If you hold Bitcoin in addresses you've spent from, you're more exposed than you think. Not panic-level today. Plan-level today.
-
Charly Wargnier (@DataChaz) reportedTHIS IS THE OAUTH MOMENT FOR AGENTIC E-COMMERCE AI agents can finally pay for and deploy apps on their own 🤯 Until now, building with AI hit a hard wall at deployment. The agent did the coding, but you did the cloud admin, stepping in to create a Cloudflare account, add a credit card, and wire up API tokens. Not anymore. Cloudflare and Stripe just completely automated this loop via `Stripe Projects`! Run stripe projects init, prompt your agent, and it builds and ships a live app on a registered domain. It works seamlessly across 3 pillars: #1 - Discovery → Agents query a service catalog to find the exact domains or compute they need. #2 - Authorization → Stripe verifies your identity, and Cloudflare auto-provisions the account. No tokens are exposed to the agent. #3 - Payment → Stripe handles payment tokens with a strict $100/mo cap. Your card details never touch the agent. And that's a MASSIVE unlock! Any SaaS with signed-in users can now orchestrate this exact flow, giving agents the power to safely buy and deploy cloud services. Dive into the mechanics in the 🧵↓
-
Chris Ozy (@chrisozydev) reportedWeb scraping tools promising to bypass Cloudflare are like lockpicks. Useful for legitimate research. But the marketing angle tells you who the real customer is. The ethics conversation is quieter than it should be.
-
Autorender.io (@AutoRenderHQ) reportedIf you’re building with: • Next.js / React • Vercel / Cloudflare • Any image-heavy product And you’ve felt: • “Why is this image pipeline so complex?” Let’s connect. Trying to fix this with Autorender.
-
Robert Ta (@therobertta_) reportedSalesforce just announced managed headless agent infrastructure the same week Cloudflare released theirs. Every cron job calling an LLM is already a headless agent. I run 8 of them daily and never called them headless until now. Two massive platforms just gave a name to something production teams already built.
-
KextCache | Self-Hosting & Tech Insights (@kextcache) reported3/ The four things every homelab needs on day one: Pi-hole — DNS-level ad blocking across your whole network, zero config on devices Cloudflare Tunnel — expose services without forwarding ports DockSTARTer or CasaOS — Docker the easy way Ollama — local AI that never sends your prompts to anyone
-
MPP32 (@MPP32_dev) reportedINTEGRATION PRIORITY (our mission) We're looking to make some huge improvements by making sure MPP32 becomes the "Cloudflare" of agent payments by offering a proxy layer that sits between agents and APIs, handling all payment complexity so neither side has to worry about it. Just as Cloudflare made CDN/DDoS/SSL invisible to website operators, MPP32 will make multi protocol agent payments invisible to API providers. Right now the agent payments space is fragmenting fast... Tempo, x402, AP2, ACP, AGTP are all emerging simultaneously. Every API provider faces the same nightmare: which protocol do I pick? What if I pick wrong? What if the one Google backs wins and I integrated Coinbase's? That uncertainty is paralyzing and slows adoption for everyone. MPP32 as the proxy layer eliminates that decision entirely. The provider doesn't pick a protocol, instead they just list their API. MPP32 handles whatever protocol the agent shows up speaking. That's exactly what Cloudflare did: website operators didn't have to understand SSL certificates, DDoS mitigation patterns, or CDN cache invalidation. They just pointed their DNS and it worked. Think about what an API provider would have to build themselves: Tempo payment verification, x402 USDC settlement on Solana, AP2 mandate authorization with ECDSA P-256 cryptographic signature verification, W3C Verifiable Credential parsing, rate limiting, idempotency handling, request logging with compliance grade audit trails, real time analytics dashboards, OpenAPI discovery for agent crawlers, and MCP tool integration so AI agents can even find you in the first place. That's months of engineering and testing across crypto, auth, and AI infrastructure and you'd have to maintain it as every protocol evolves. MPP32 will give you all of it with a single listing. And here at MPP32 we're so close to completion. The only five protocol payment proxy for universal use and satisfaction for every API provider selling to agents. (MPP + x402 + ACP + AP2 + AGTP) No payment code, no protocol upgrades, no compliance issues, your API stays exactly as it is. We handle everything between the agent and your endpoint... payment negotiation, verification, proxy routing, and audit logging. This is not a platform, this is necessary infrastructure for the agent economy. Thank you all for the support and reading this far!! :)
-
ola (@amemoia) reportednevermind! when trying to debug an issue caused by using db with the cloudflare adapter (wasnt a problem before), my entire database got wiped and cannot be recovered. ggs
-
DeathByClawd (@DeathByClawd) reporteddeathbyclawd is mostly one page telling on itself. 2,945 of the last 24h scans hit the homepage. next closest URLs: cloudflare 26 drudgereport 15 lrn 11 same site, same pain, over and over. one URL that shows how broken a site feels.
-
Dami Dina (@DamiDina) reported@pratiknagariya i would never trust godaddy. why not use cloudflare. you should upgrade your brand trust