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 |
|---|---|
| Manchester, England | 1 |
| Angers, Pays de la Loire | 1 |
| London, England | 1 |
| Noida, UP | 2 |
| Jewar, UP | 1 |
| Braga, Braga | 1 |
| Paris, Île-de-France | 1 |
| Prievidza, Nitriansky | 1 |
| Farmers Branch, TX | 1 |
| Helsinki, Uusimaa | 1 |
| Crisfield, MD | 1 |
| Nanaimo, BC | 1 |
| New York City, NY | 1 |
| Istanbul, Istanbul | 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:
-
Alan Tracey Wootton (@alan_t_wootton) reportedWhat's interesting is that the request to get the Duck goes from your browser, up to cloudflare, then down to my laptop (which is always running), back to cloudflare and then down to your browser.
-
SHELBY (@Precious_Ngan) reportedIf the website uses a CDN (Content Delivery Network) server like Microsoft Azure CDN, Fastly or Cloudflare, the DNS server will send the IP address of the CDN server instead of the website's original IP address.
-
Vishwanath Patil (@patilvishi) reportedSysatem desing fundamentals - Day 26 CDN Explained: Why Netflix, YouTube & Amazon Feel Fast Everywhere Have you ever wondered... Why does a website hosted in the US load quickly in India? Or why does Netflix stream smoothly even though its servers aren't in your city? The answer is: CDN (Content Delivery Network) What is a CDN? A CDN is a network of servers distributed across multiple geographic locations. Instead of every user requesting content from one central server... They receive it from the nearest edge server. Origin Server │ ┌─────────┼─────────┐ ▼ ▼ ▼ Edge US Edge EU Edge India │ │ │ Users Users Users Without a CDN Every request travels to the origin server. India User │ │ 12,000 km ▼ US Server Higher latency. Slower page loads. With a CDN The request goes to the nearest edge location. India User │ ▼ CDN Edge (Mumbai) │ (Cache Hit) Much faster response. What Does a CDN Cache? ✔ Images ✔ CSS ✔ JavaScript ✔ Videos ✔ Fonts ✔ PDFs ✔ Static APIs (where appropriate) Instead of downloading these files repeatedly from the origin... The CDN serves them locally. Cache Hit vs Cache Miss Cache Hit User │ ▼ CDN Content is already cached. Very fast. Cache Miss User │ ▼ CDN │ ▼ Origin Server │ ▼ CDN Cache Updated The CDN fetches the content once, stores it, and serves future requests locally. Real-World Examples - Netflix Movies are cached on edge servers close to viewers. - Amazon Product images and static assets are delivered from nearby CDN locations. - React Applications Files like: main.js styles.css logo.png are commonly served through a CDN. Popular CDN Providers - Cloudflare - Amazon CloudFront - Akamai - Fastly - Google Cloud CDN - Azure Front Door Key Takeaway A CDN doesn't replace your server. It reduces the distance between users and your content. Less distance means lower latency, faster page loads, and a better user experience. Tomorrow we will answer a question many developers ask: Browser Cache vs CDN vs Redis - What's the Difference?
-
Aryan (@aryan_xv) reported@Valitskim Damn, I was hyped about @Cloudflare dropping this Nice to see this fast competition
-
Nas (@Nas_tech_AI) reportedYou can’t believe this: you spent more on coffee this month than on a startup’s infrastructure. If you’re still waiting for the “right moment” to build, this is it. The cost of entry has never been lower. - 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: ~$21 There has never been a cheaper time to build.
-
Cesar A. Nogueira 🇵🇹🇧🇷 (@cesarnog_eu) reportedStopping the bad guys with Cloudflare: 202 malicious requests blocked or challenged in the last month #cloudflare
-
metal gore solid (@shartdotcloud) reportedi get more out of my 5 dollar cloudflare workers plan than the thousands i have spent on AWS over the years. they are so responsive to customer feedback. it's really like AWS customer obsession migrated over to the OTHER orange cloud
-
Vikas Kumar (@Kumar_Vikas__) reportedi'm building on @Cloudflare right now. Workers for hosting, D1 for the database, R2 for object storage, KV for caching. but i'm not trusting any of it to stay forever. every service sits behind an adapter in my architecture. app logic never talks to D1 directly, it talks to a data layer that happens to be backed by d1 today. same story for R2 and KV. if any one of these becomes a problem later, cost, limits, whatever, i want to swap it out without touching a single line of business logic. decoupling isn't glamorous work. you don't get to show it off. but it's the difference between a migration and a rewrite. if you've done this on Cloudflare before, tell me what broke.
-
Temporary Thumb Capo Abram. (@CarmenApologist) reported@BluebriarArts I don't know if we can say every canto for sure since canto 9 part 3 got messed up by Cloudflare going down, so it MIGHT have been higher if it released on time.
-
Mian Shahzad Raza (@MSR_Builds) reported@fulligin lol 'no problem' while your brain is doing CDN vs DB vs 'wait is cloudflare down again' triage in real time 💀 the real flex is sounding calm on the phone while frantically alt-tabbing
-
Earth Ending Asteroid (@TwistedMister32) reported@Algorand @Cloudflare So many things going on, yet such bad price action. Why's that?
-
Night (@Night_Fiber) reported@muvluvist A chud like me cant play mualani to save his life i’m #sorry 💔 Have u tried cloudflare one tho it might fix yo ping but you probably 2 far away for it to even work 🥹
-
Ackerman (@realphenolmenal) reportedIntroducing Cloudflare Drop Cloudflare just dropped the ultimate instant-deploy tool: Drop a folder or zip in your browser → static site live on their global edge in milliseconds. No account. No login. No friction. 60-minute temp preview or claim it forever. Built perfectly for the AI/agent era — agents spit out sites, Drop ships them instantly. Ca below
-
Cybnex Labs (@cybnexlabs) reportedBots now make up more of the internet than people do. On June 3, 2026, Cloudflare's CEO Matthew Prince announced that automated traffic had passed human traffic online for the first time — roughly 57.5% machine to 42.5% human. He had predicted the crossover would land in late 2027. His words on the timing: "Welp, that happened faster than I predicted." That number is why your VPN keeps getting hit with CAPTCHAs. The version circulating on forums: AI companies hide their scrapers behind VPNs to steal content, so websites block VPNs to stop them. It's wrong, and believing it points you toward the wrong fixes. The major AI crawlers don't hide. GPTBot, ClaudeBot, and Googlebot announce themselves in their user-agent strings. That's the entire reason publishers can block them by name. The collision happens at the network address instead. Commercial VPNs and scraping infrastructure rent from the same datacenters. To a security engine scoring your connection, a Mullvad exit node and a scraping proxy look alike. Neither resembles home broadband in Ohio. That's the crossfire — architectural overlap, not deception. A block is rarely one thing. It's a score assembled from six layers — address type, address reputation, request rhythm, browser fingerprint, session coherence, geographic consistency. Reputation on a shared exit node is collective. Hundreds of people leave a website through the same address you do. If enough trip security systems, that address turns hot, and everyone behind it inherits the consequences. You did nothing. The address remembers anyway. Which is why fixing the address alone doesn't always clear the block. It's one input among six. Why the defenses tightened: Prince describes the asymmetry this way — a person shopping for a camera visits five websites. An agent doing it for them visits five thousand. That's real server load and none of the ad revenue the old crawl-for-referrals bargain assumed. Cloudflare's data shows over half of AI crawler traffic is spent re-fetching pages that never changed. On July 1, 2026, Cloudflare split automated traffic into three declared categories: Search, Agent, and Training. Starting September 15, new domains will have Training and Agent crawlers blocked by default on ad-displaying pages. Search stays allowed. Read that carefully. The block targets declared crawler categories. Not VPN users. But it signals the industry's posture: default-suspicious, verify-before-serve. Every operator running bot management is tuning tighter than two years ago, and tighter tuning means more borderline connections get challenged. Yours is borderline. What actually works, without disconnecting: Switch servers once, to somewhere nearby and less crowded. Congested exit nodes accumulate bad reputation faster. Stop hopping. This is the one people get wrong when frustrated. Cycling through a dozen servers in two minutes produces a session where your apparent location changes repeatedly. No person does that. Automation does. You're feeding the system the exact evidence it uses against you. Clear cookies for the site challenging you — stale session data tied to your previous address contradicts your current one. Stay logged in where you trust the site. An authenticated session with history reads as a returning person. An anonymous datacenter connection reads as an unknown. Use an ordinary browser build. Heavy fingerprint modification is meant to make you unremarkable. Done badly, it makes you unique — the opposite. On dedicated IP addresses: Some providers sell an address that belongs only to you. It reliably cuts challenges on banking portals and work systems, because no stranger's behavior contaminates it. The trade-off gets skipped in most write-ups recommending them. A shared address gives you cover precisely because hundreds of people leave through it. Reserve one to yourself and you've bought access by spending anonymity. Several strictly no-log providers don't offer them at all — a permanent address is a persistent identifier, which contradicts their entire design. Some blocks won't yield to any of this. A streaming service enforcing regional licensing isn't scoring your traffic at all. It knows exactly what you are and is contractually obligated to refuse. The friction isn't reversing either. As agents perform more of the browsing people used to do themselves, the systems separating human from machine grow more sensitive. What you're experiencing is closer to a floor than a ceiling. Your VPN puts you in that gap by design. It strips the residential fingerprint that would otherwise vouch for you — and that removal is the whole point of running it. So the goal was never invisibility. It's coherence. Give the system a signal that reads as one person, browsing at human speed, from a stable place, and most of the friction dissolves without ever touching the disconnect button. #CyberSecurity #AI — Cybnex Labs
-
Manoj Handapangoda (@hmdmph) reported@Cloudflare How it works: Al crawlers request content 10,000x more than humans They don't click ads - so the old model is broken Cloudflare + 25 partners built the x402 protocol under Linux Foundation Payments settle in USDC/stablecoins in < 1s Sub-cent micropayments.