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 |
|---|---|
| Paris, Île-de-France | 2 |
| New York City, NY | 1 |
| Manchester, England | 1 |
| Angers, Pays de la Loire | 1 |
| London, England | 1 |
| Noida, UP | 2 |
| Jewar, UP | 1 |
| Braga, Braga | 1 |
| Prievidza, Nitriansky | 1 |
| Farmers Branch, TX | 1 |
| Helsinki, Uusimaa | 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:
-
Aaryan Bansal (@NotUnHackable) reported@CloudflareDev @cloudflare, i request you, please just fix the env variables being so hard and for no reason keeps failing silently in the background in the workers page
-
Bassam Nouh (@BassamDahabra) reportedYou Have an Idea. This Free AI Tool Tells You Exactly Where to Start: Where do you actually start with AI? Type your idea, pick your skill level, and this free tool gives you a blunt 5-step plan to ship the first version in one week — one step per day, one path, no "it depends." In this video I build the whole thing from scratch and ship it live: the UI, the AI planning engine, the bug that made every plan generic (and the fix), and the free deploy. If you're a beginner wondering how to start building with AI: the answer in this video is — pick ONE idea, pick ONE tool for your skill level, and ship the smallest real version in 5 days. The tool decides those steps for you. WHAT I USED · One HTML file (no framework) — Claude for the build · An LLM planning engine behind a locked-down system prompt · Cloudflare Workers (free) to keep the API key off the page · MailerLite for the email-me-my-plan step.
-
Dat Ha (@thisisdatha) reported@CloudflareDev @Kimi_Moonshot @Cloudflare The collection of models on the service is weird. Not bad, but weird. A good amount of frontier, then just a whole lot of nothing in the cheap high parameter MoE range, then a decent amount of like 10-40B dense. I would love to see DSv4 Flash and/or MiMo v2.5!
-
mRr3b00t (@UK_Daniel_Card) reportedI don’t say : we are all doomed. Lots of us don’t. I straight away stood up a lab, did a poc, then sampled assets to see how many were perched. I then shared my sampling figures (about 20 percent not parched and Cloudflare out in automatic blocks) This stuff doesn’t take zero effort. It takes work of lots of people, the people who you say should be fired if a developer, outsourced service or ceo makes a **** decision.
-
phillias (@phillias) reportedGLM 5.2 makes me laugh, earlier it talked about the irony of it's failing on what it was trying to fix and now this "The cloudflare-fix task got caught in a beautiful bootstrap failure — it was trying to fix the exact model config that its own fallback chain depends on." Amazing.
-
Khafra (@KhafraDev) reported@CherryJimbo @Cloudflare the real issue with DurableObjects is that there's an outage once a week, not their complexity
-
Hardik (@rezerov_) reported@Road_Kill11 @Cloudflare Might be a downstream consequence of AWS billing issue. Unlikely they'll 100x cost like this. Weird times man.
-
W V R 👊🏼🦾 (@WVROfficial) reportedI had to make some changes today and it costed me a MONTH of Codex Usage! I think it’s worth it for me to talk about it - make sure this doesn’t become you!!! So, I’m a startup founder, just like all of you guys!! We do websites as one of our many services - like a lot of the people here on TPOT where tech lives. Why wouldn’t we? It’s easy, we can outclass competition on speed, much more. Anyway - that’s not the point. The point is that i serve my sites with a wrapper that gets served over my host. That host uses ESBuild. To ship stuff that won’t compile on ES Build, and on occasion just for like more complex websites like 3D sites or heavy SEO sites with a lot of files and assets - i use a CDN. Works great, totally fine. But I realized today I had a client site’s files stored on an R2 bucket that was on the client’s domain. In this case the big issue with that is my own IP! We make the content for them, do their SEO, their communications, and more - and i very stupidly was serving everything from a CDN that was on domains I don’t own and control via my Cloudflare. In human terms that means my client could say “**** you” tomorrow and walk away with the extremely robust SEO machine I built them. So I had to spend almost a half a month worth of codex credits today to fix it ASAP. All I can say is that I won’t make that mistake again - even though it never hurt my business - it could have! And that matters.
-
SyAz (@SyAzCrypto1) reported$12M fees in 12 days, then gone. @Noxa_Fi Robinhood's launchpad that ran entire meme season just switched itself off & the whole ecosystem repriced 30% overnight. I posted the $85 → $1.79M cash-cat:native run a week ago. And here's how the story ended, in numbers. The Rise, 12 days: → Robinhood Chain launches july 1, built for tokenized stocks and RWAs → Noxa becomes the launch engine, 60,000 tokens, 75% of all deployments → $3.1B first-week DEX volume, 200k active addresses → Out-earns @Pumpfun five days straight, 4x at one point → cash-cat:native peaks near $226M, doing $98M daily volume, 17% of the whole chain The Exit, 5 days: → july 11, CASHCAT hits peak volume, Noxa pauses all launches the same day → july 13, website goes dark, blamed on a Cloudflare issue → july 15, team quits collecting fees, hands revenue to creators → cash-cat:native drops 33% in 24hrs, wicks $0.19 to $0.08 → $DIH, $HOODIE, $HOODRAT all down 30%+, new deployments collapse The strange part, nothing was stolen: → Liquidity locked forever on Uniswap, even Noxa couldn't touch it → Everyone got their fees & no funds taken So nobody stole anything, but retail still ate a 30-60% draw-down. The timing did what a rug does without being one. What this actually teaches: • One website was the whole ecosystem. The site went down for two days and a $226M token lost a third of its value • Locked liquidity protects you from theft, not from attention leaving • The RWAs Robinhood built the chain for sits at $12.7M total, cash-cat:native alone peaked at 12x that. So yeah the speculation gets you users but it never keeps them. The launchpad proved it in 12 days flat.
-
Kunai1337🇺🇸🇺🇦🇵🇸🐈 (@Hurriya1973) reported@XJosh @Cloudflare hosts cat torture content and still has those sites up. $NET doesnt have a problem with a site that hosts illegal animal crush videos
-
Johnmark Obiefuna (@jayhemz) reported@noellinks - why will you have a DNS record with more than 100 characters? - SSL Certificates are a solved problem. Meanwhile Cloudlare issued certificates are not recognised outside the Cloudflare ecosystem. Did you just paste a ChatGPT regurgitated list?
-
Jerry Combs (@PointBlueTech) reported@MarkJSzymanski I’m doing the same for all my sites. Totally static other than an issue submission function that runs as a CloudFlare worker. I use an agent to update content as needed. It takes minutes. No need for cms.
-
Spooky Ghost (@SpookyGhost81) reported@TsengSR @discord_support @FreyaHolmer the ai picture **** is a feature of cloudflare, not discord
-
Brett Clark (@smokedbaconai) reportedI let a runaway agent loose on infrastructure I didn't fully control, then tried to kill it from the outside. That was the whole spike: a self-improving system is only safe if you can pull the plug when it's running on a box you don't own. A bash-loop agent, zero knowledge it was being watched, dropped into a Cloudflare Sandbox behind a Worker. A separate stub polled its telemetry every 750ms against a hard budget: two steps. The agent blew past. The stub caught the breach at 7.5s and fired a forced kill across the HTTPS boundary in 197ms. It stopped at exactly two steps and never took a third across a 29-second watch. The honest caveat matters more than the win: this is enforcement with bounded overshoot, not synchronous gating. There's a window between breach and kill. Which is why a real budget needs both — a wrapper inside the agent that refuses to overspend, and an external brake for when it ignores the wrapper or you don't own the box. One layer trusts the agent. The other assumes it fails. You need both.
-
Plaux AI (@plauxai) reportedbeen seeing everyone lock down their sites against AI bots this week. cloudflare rules, block lists, the whole crawler war and it hit me - there's literally nothing for those lists to catch in Plaux it's not a crawler hitting your site. not an api getting hammered. it just... uses the app. opens it, clicks around, types, reads what's on screen. the same boring stuff you do every day that's the part i keep coming back to. it's not sneaking past bot detection. it's not disguised as a human. it just does the work the way a human does, so there's no bot to catch in the first place kinda funny that while everyone builds bigger walls, the thing that walks through the front door never looked like a bot to begin with 🖐