1. Home
  2. Companies
  3. Cloudflare
  4. Outage Map
Cloudflare

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

Loading map, please wait...

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:

Less
More
Check Current Status

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
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 2
Frankfurt am Main, Hesse 2
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
Eastleigh, England 1
New Orleans, LA 1
Mainz, Rheinland-Pfalz 1
San Miguel de Tucumán, TM 1
Check Current Status

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:

  • craigwarmke
    Craig Warmke (@craigwarmke) reported

    "Lelli's result is the practical counterpart to those optimizations. The distance from 15 bits to 256 bits is large, but the gap is increasingly viewed as an engineering problem and not a fundamental physics problem." The 2029 transition deadlines from Google and Cloudflare look more responsible than ever. The people saying there's a 0% chance of q day, even within ten years, look increasingly irresponsible. I hope we can collectively update our probabilities and throw support behind developers. It will be tempting to punish and humiliate people whose probability judgments have gone the wrong way. But we'll be better off if we don't block the exits.

  • JakwounReid
    Jakwoun Reid (@JakwounReid) reported

    My rate limiter was silently broken in production for months. It deployed fine. It tested fine. It ran fine. It was also completely useless. Here's what I found, and how I fixed it by rebuilding on Cloudflare Workers.

  • patilvishi
    Vishwanath Patil (@patilvishi) reported

    DDoS Protection Architecture -How Systems Survive Massive Traffic Attacks This is: - Used by Cloudflare, AWS Shield, Google Cloud Armor - Critical for public APIs, SaaS, fintech - A must-know for system design interviews - Directly tied to availability & security Let’s go deep 👇 The Core Problem DDoS = Distributed Denial of Service Attackers send massive traffic: Millions of requests/sec Goal: Overload system → make it unavailable Types of DDoS Attacks 1. Volumetric Attacks Flood network bandwidth. Example: UDP flood, DNS amplification 2. Protocol Attacks Exploit network layer. Example: SYN flood 3. Application Layer Attacks (Most Dangerous) Look like real traffic: HTTP GET /login spam Hard to detect. Defense Strategy (Layered Approach) DDoS protection is not one tool. It is multi-layer defense: 1. Edge Protection (CDN + WAF) First line of defense. Handles: - Traffic filtering - Bot detection - IP blocking - Geo-blocking Examples: Cloudflare Akamai AWS CloudFront + WAF 2. Rate Limiting Limit requests per IP / tenant. Example: 100 req/sec per IP Stops abuse early. 3. Load Balancing Distributes traffic across servers. Prevents single-node overload. 4. Auto Scaling Increase capacity during attack. But: Scaling alone does NOT stop DDoS. 5. Application Protection - CAPTCHA - Login throttling - API key validation - Token-based access 6. Backend Protection - Circuit breakers - Queue buffering - Caching Example Attack Flow Without protection: Botnet → API → DB → crash With protection: Botnet → CDN → WAF → Rate Limit → App → DB Attack filtered before reaching backend. Key Techniques 1. IP Reputation Block known bad IPs. 2. Geo Filtering Block traffic from suspicious regions. 3. Bot Detection Analyze: - request patterns - headers - behavior 4. Challenge Systems - CAPTCHA - JS challenges - Proof-of-work 5. Traffic Shaping Limit heavy endpoints like: login search payment Real-World Example Login endpoint under attack: 1M requests/min Protection: - CAPTCHA after 3 attempts - Rate limit per IP - Block suspicious patterns Trade-Offs Strategy Benefit Cost CDN/WAF Strong protection Cost Rate limiting Easy May block legit users CAPTCHA Blocks bots UX impact Auto scaling Absorbs load Expensive Architect-Level Insight DDoS protection is about: Filtering early + protecting deeper layers Never rely on backend alone. Common Mistakes - No edge protection - Only scaling infra - No rate limits - No bot detection - Blocking too aggressively Golden Rule Drop bad traffic as early as possible Edge > Gateway > App > DB Final Insight DDoS protection is not optional. It is a core reliability + security requirement for any internet-facing system.

  • My1xT
    My1 (@nep.one - Misskey) (@My1xT) reported

    @Cloudflare At least some more stuff needs to bette work with dynamic gua prefixes. This was one major issue where i worked with a firewall software which didn't seem to like them.

  • sergiukazak
    Sergiu Cazac (@sergiukazak) reported

    @Atinux @lightpanda_io I was very excited but Cloudflare blocks it right away and it breaks on most sites, cause a lot of sites use APIs that it still doesn’t support.

  • JonasRefseth
    Jonas Myhr Refseth (@JonasRefseth) reported

    @Cloudflare Of course! My ISP is launching support in the spring of 2025! 😵‍💫

  • irbaazkadri
    Irbaaz Kadri (@irbaazkadri) reported

    @Cloudflare @CloudflareDev @GoDaddy Even at the end of 1 hour they still can't fix it.

  • ethicalyaoifan
    Bryce in the HOUSE (@ethicalyaoifan) reported

    @pussyluvrr69 the internet archive link is down the piracy site i was watching it off was apart of a cloudflare raid that shut down 900 websites the websites that arent shut down dont have it IM WATCHING IT ON MY PHONE SO I CANT EVEN TORRENT 😭

  • Blocky256
    bL●CKY (@Blocky256) reported

    @MegaBasedChad this has always been the case tbh. if you have a website, expect bots to be attempting this all the time. Along with well configured server, Cloudflare is a good starting to point to help protect yourself.

  • HaloArchive
    HaloArchive (@HaloArchive) reported

    Anyone prior to 11:15 am EST 04/24 is approve. Go Register. Drop a DM or Discord with your email if you have issues. If Cloudflare block send RayID or IP.

  • dh14151617
    dh1415161(new) (@dh14151617) reported

    @Cloudflare dealing with cloudflare is like fighting a hydra, after other people spends ages having to fix the **** that cloudflare keep breaking they **** up even more stuff making every company stupid enough to use cloudflare lose much bussiness and money

  • chynen_eide
    Chynen Eide (@chynen_eide) reported

    I have to admit. Cloudflare is awful. Firstly, security verification: most of the websites get a verification if you are not a bot and that's fine. The problem is that it failed to load (it refreshes over and over and over again). Then if you think that's bad, Some websites get down.

  • sinasanm
    Sina Meraji (@sinasanm) reported

    2 incoming PRs today (custom slash commands PR from @seasonsaw, and cloudflare AI gateway support from another legend). thank you

  • dh14151617
    dh1415161(new) (@dh14151617) reported

    @Cloudflare dealing with cloudflare is like fighting a hydra, after other people spends ages having to fix the **** that cloudflare keep breaking they **** up even more stuff making every company stupid enough to use cloudflare lose much bussiness and money

  • cumulus_____
    Cumulus (@cumulus_____) reported

    @CodeWithAmann Always vercel, anything backend related render. If heavy and need speed aws Never ever Cloudflare, just not curious to learn it and I don’t understand their pricing

Check Current Status