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 |
|---|---|
| New York City, NY | 3 |
| Los Angeles, CA | 1 |
| Paris, Île-de-France | 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:
-
Nick Blow (@NickBlow) reported@hackerdocc Vercel’s main value prop was making AWS easier to use but with agents they kinda solve that problem already, trivial to do some iac stuff. Fluid compute is genuinely pretty cool and not many companies compete - though vercel is still v v expensive even with the efficiency there. Cloudflare skirts the issue by charging for CPU vs wall clock. Cloud run and lambda managed instances are *sort* of analogous but not quite.
-
XYZCloud | Creator Platform (@XYZCloudHQ) reportedStopping the bad guys with Cloudflare: 2,704 malicious requests blocked or challenged in the last month #cloudflare
-
Welldone (@welldone_tech) reportedCloudflare shipped WriteGuard for MCP servers: agents can read data, write operations need an explicit gate. Unrestricted tool access is the actual production risk with agents - not that the model is wrong, but that a prompt injection or a hallucination reaches a database that never should have been writable in the first place. Read/write separation for agents isn't a Cloudflare feature. It's the same principle behind every gate we put in our own process - a senior approves the spec before code exists, a different model reviews it, an engineer deploys manually. The tool doesn't get more trust than the person watching it.
-
Kashperskyi Y. (@EKashpersky) reported@tarkov @nikgeneburn Cloudflare error in html in the game. Come on! There has to be a better way handling errors. Peace
-
Don Codeleone (@MrDonCodeleone) reported@__kutluk @mrfundman I can think of use cases, but if it can't even handle a basic task like working on a Shopify store because it's hard-stuck on login, then it's useless. Literally blocked by most Cloudflare CAPTCHAs, and they have zero way around it. Meanwhile, Codex breezes right past it.
-
JohnNguyen 🔆 (@ThuyTrang108) reportedThe next wave of crypto users might not be humans, but AI. As AI agents become increasingly capable of autonomously searching for information, calling APIs, purchasing data, and executing tasks on behalf of humans, they require a way to make payments and stablecoins are emerging as a highly suitable option. Coinbase’s x402 protocol has processed over 165 million transactions totaling approximately $50 million; nearly 99% of these utilized USDC, with an average value of just around 30 cents per transaction. These figures signal the formation of an entirely new market: millions of automated, 24/7 micropayments occurring between software systems. As major players like Visa, Mastercard, Cloudflare, and MoonPay begin building infrastructure to facilitate payments by AI agents within controlled limits, stablecoins could evolve beyond mere money-transfer tools for humans to become the payment system for the AI agent economy.
-
adha adha aja (@adharid21) reported"yo router is on fire, too much traffic" "yea use Anycast then scale across multiple data centers." "bro IXP links are cooked edge is down" "yea put Cloudflare / Akamai CDN in front and drop 90% of requests at the edge."
-
Adithya 🚀 (@adithyashreshti) reportedWTF, @Namecheap. Need recommendations. For YEARS, I’ve recommended Namecheap over GoDaddy because the support was great and I trusted the experience. Now I’m finding that EVERY SINGLE domain I searched on Namecheap’s WHOIS less than 24 hours ago is suddenly “taken.” Not one. Every. Single. One. People on Reddit raised this exact issue months ago. I defended Namecheap because I’d never experienced it myself and even mentioned it is trust worthy. Well, I faced it now. I searched each domain ONCE. Just once. I wasn’t repeatedly checking them or trying to register them. And now they’re all “taken.” Maybe it’s a coincidence. But it’s a pretty damn weird one because every domain I that I had checked for availability is gone at easily 10x the price. I’m seriously considering moving everything out of Namecheap. Who are you guys using instead? Already using Cloudflare for .com, but I still have a lot of domains at NC.
-
YanXbt (@IBuzovskyi) reportedHERMES AGENT HAS AN AUTONOMOUS SKILL MANAGER RUNNING IN THE BACKGROUND. IT PRUNES WHAT YOU DON'T USE. IT ARCHIVES WHAT'S STALE. IT'S CALLED THE CURATOR. every time your agent solves a new problem and saves a skill, that skill lands in ~/.hermes/skills/. month 1: 15 skills. manageable. month 3: 47 skills. some are near-duplicates. month 6: 90+ skills. half are stale. catalog bloated. tokens wasted every turn loading skill headers the agent never calls. the Curator cleans this up automatically. HOW IT WORKS: tracks every skill: how often viewed, used, patched. 30 days unused → marked stale. 90 days unused → moved to archive. archived skills go to ~/.hermes/skills/.archive/ never deleted. always recoverable. runs every 7 days. enabled out of the box. WHAT IT TOUCHES: agent-created skills: full lifecycle. stale, archive, consolidate, patch. bundled built-in skills: archived after 90 days of non-use (on by default). hub-installed skills (agentskills. io): NEVER touched. off-limits. WHAT IT DOES NOT TOUCH: memory files. USER.md and MEMORY.md are not managed by the Curator. people confuse this constantly. Curator = skills only. PIN YOUR CRITICAL SKILLS: hermes curator pin deploy/cloudflare-pages pinned = off-limits. no stale. no archive. no consolidation. skill_manage refuses to delete it. patches still go through (agent can improve content). only agent-created skills can be pinned. skills in any cron job's skills: list are also protected without explicit pin. COMMANDS: hermes curator status (state + 5 least-used skills) hermes curator run (manual run now) hermes curator run --dry-run (preview without changes) hermes curator pause (stop auto-maintenance) hermes curator resume (restart) hermes curator pin [name] (protect) hermes curator unpin [name] (remove protection) hermes curator backup (manual snapshot) hermes curator restore [name] (recover archived skill) hermes curator rollback (revert last run) also available as /curator inside any session. LLM CONSOLIDATION (off by default): opt-in auxiliary model pass that reviews your skills for overlaps and proposes merges. curator: llm_review: true WARNING: run --dry-run first. always. auto-consolidation can merge skills you want to keep separate. comment CURATOR and I'll send you the full checkup guide with 5 use cases and config templates for solo dev, multi-project, and team setups.
-
Onur Genes 🐺 (@onurgenes) reported@jonathan_wilke also probably someone reported it. cloudflare first takes down the website and then asks you to prove that your website is not fraud. you should definitely check that
-
Rishabh (@crashedrishabh) reportedDay 20 Electron app is now rock solid. Spent the day making it crash-proof — better error handling, safer process management, cleaner shutdown. It's not going down easy anymore. Started the Mac version build. Same codebase, platform-specific tweaks. This is where cross-platform gets real. Dived into Cloudflare Workers + Hyperdrive + Redis. App files served from the edge, cached in Redis for faster downloads. Learning how CDN-level speed actually works under the hood. LC 1386 done. 20 days. Still shipping daily. No plans to stop. @kirat_tw @100xDevs @100xSchool #buildinpublic #electron #cloudflare
-
Pikanou ⚡🏴☠️ (@pikanou_) reportedAgent Experience is quite a terrible label since AI doesn't have, urgh... feelings. So repurposing human-centric 'UX' terminology for autonomous agents is weird and just plain buzzword. Sounds like AX is the new UX! Rebuild everything! But behind the scenes, the engineering is a big reality. For now most websites are hostile to AI agents, quite difficult for them to visit the pages with cookies banners, cloudflare bot challenges, client-side JS hydration crash headless scrapers before they even fetch content. What we see from Vercel with their isagentic is about improving your website for Machine Accessibility. Agents don't care about the design of your landing page. They just want to extract its content. Want to know what to do? -> building deterministic APIs, agent-first auth, and machine-readable data pipelines. I would call it instead Agent Interoperability, but yeah I guess you can't brand it as "AI"
-
Drayken (@KGDrayken) reported@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.
-
Matthieu H. (@twMatthieuH) reportedThe stack: React Native + Expo, TypeScript, Hono on Cloudflare Workers. Boring on purpose. And AI-assisted everywhere: coding, support replies, content, ASO. When you have a few hours per week, you don't want to fight your tools.
-
Shadooow (@ShadooowOnX) reportedAndrej explains why Grass needs your internet connection, not your personal data "Anyone joining the Grass network isn't actually sharing personal information or anything like that. I do feel like that ends up being this wide misconception" "Ultimately, what they're contributing is just internet bandwidth" "When AI labs need to build huge training datasets to train their AI models, the most important source for them is actually the internet. They need to go and read as much of the internet as possible" "We're living in a world right now where even though the internet's growing at an exponential pace, the rate at which it's shutting off to the public web is also growing at an exponential pace" "Basically a third of the internet right now is getting protected by Cloudflare. If any AI lab wants to scrape websites that have these types of anti-bot turned on, that is completely inaccessible to them" "Any website that sees an IP address belonging to any of the top frontier labs or any of the cloud providers nowadays is just blocking those" "Grass is a network of millions of residential internet connections" "What we've built is the ability for any AI lab to tap into millions of IP addresses so that all their crawling activity looks like real user activity, and websites display data that they would otherwise display to residential users" "This is all public data, by the way. Nothing behind login walls, nothing behind paywalls. This is all public data that should remain public"