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

cloudflare Hero Image

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.

Map Check Current Status

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Berlin, Land Berlin 3
Frankfurt am Main, Hessen 2
Paris, Île-de-France 2
Ulm, Baden-Württemberg Region 1
Merlo, BA 1
Eastleigh, England 1
New Orleans, LA 1
Mainz, Rheinland-Pfalz 1
San Miguel de Tucumán, TM 1
Villa Crespo, CF 1
Aguascalientes, AGU 1
Köln, NRW 1
Trondheim, Trøndelag 1
Derry, Northern Ireland 1
Maceió, RJ 1
Neu-Ulm, Bavaria 1
Hamburg, HH 1
Altavilla Vicentina, Veneto 1
Victoria, BC 1
Madrid, Comunidad de Madrid 1
Brussels, Bruxelles-Capitale 1
Padova, Veneto 1
Madisonville, KY 1
Central, NM 1
Maple, ON 1
Vitry-sur-Seine, Île-de-France 1
Sargans, SG 1
Jewar, UP 1
Magdeburg, Saxony-Anhalt 1
Clermont-Ferrand, Auvergne-Rhône-Alpes 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:

  • cedwardsmedia Corey Edwards (@cedwardsmedia) reported

    @Cloudflare If it makes you feel any better, the outage resulted in fewer deaths than the Therac-25.

  • JGiegerich76578 JEFF GIEGERICH (@JGiegerich76578) reported

    @lukebelmar I for one didnt even know cloudflare went down. Hmmm interesting...

  • coproduto el hombre pulpo (@coproduto) reported

    @_Felipe @TheEduardoRFS I'm not sure, this depends on Cloudflare's priorities. I think panicking and disabling the node is a good idea if there is proper monitoring in place and if you believe that this will fix most error cases, which Cloudflare seemed to justifiably believe.

  • SteveyStevey_ Stevey. (@SteveyStevey_) reported

    @HikariSub_t Cloudflare outage caused X to have problems

  • serenicthrill freespirit (@serenicthrill) reported

    reason why cloudflare goes down ";"

  • thedatavidhya DataVidhya (@thedatavidhya) reported

    > Why Cloudflare Went Down (And How One Internal Bug Broke Half the Internet) - Everyone thought it was a massive DDoS attack, traffic patterns looked wild. - But the truth was far less glamorous: an internal config file quietly blew up in size. - That single file pushed Cloudflare’s global proxy layer over the edge. Here’s the reality: → Cloudflare didn’t get attacked. → Cloudflare attacked itself with a latent bug. > Let’s break down what really happened 👇 1. From “Suspicious Traffic” → Internal Failure • At 11:20 UTC, huge 5xx errors erupted across the internet. • Initial guess: some coordinated attack. - Actual cause: Cloudflare’s Bot Management system generated duplicate entries. → The config file that powers bot rules suddenly doubled in size. 2. From Stable Config → Oversized Time Bomb - This config is consumed by Cloudflare’s core proxy component, the thing that sits between users and the internet. - The proxy expects the file to stay within a predictable size range. • When it exceeded that limit, the proxy didn’t degrade gracefully. → It panicked and crashed, taking everything along with it. 3. From Single Crash → Global Ripple - Cloudflare’s systems automatically propagate config files across the entire network. - The moment the “bad” config got pushed, healthy servers started choking. → One oversized file → thousands of machines loading the same poison pill. → Worldwide outage triggered in minutes. 4. From Guesswork → Root Cause - Engineers saw abnormal spikes and thought “DDoS?” - But the pattern didn’t match an attack. • The underlying issue was intermittent: sometimes a good config, sometimes a corrupted one. → The real enemy was a latent bug + broken DB permissions that generated duplicates. 5. From Chaos → Recovery - Cloudflare rolled back to a “known-good” config. - Stopped the broken auto-generation. - Restarted their proxy fleet to clear the bad state. → Traffic normalized. → Internet restored. → No attackers involved, just complexity doing what complexity does. > In 2025, outages aren’t caused by hackers, they’re caused by hidden assumptions, silent bugs, and systems that scale faster than their guardrails. - Cloudflare didn’t fail because someone broke in. Cloudflare failed because one file grew bigger than the system’s worldview allowed.

  • sinsxtrgdy Eja (@sinsxtrgdy) reported

    @indigomester Yeah, the cloudflare was down and that's the main reason of why x, canva, even chatgpt down. My bad, I thought the gov shut our access to the world right after that. I bet they're just lucky.

  • mSykeCodes mSyke (@mSykeCodes) reported

    @piq9117 No because cloudflare is down

  • BeAWhale_io Dan @BeAWhale (@BeAWhale_io) reported

    Cloudflare Just Admitted Their Bots Broke the Internet On January 23, Cloudflare went down for 90 minutes. Websites across the globe stopped loading. The culprit? Their own bot management system. A configuration change in the WAF (Web Application Firewall) triggered a chain reaction that crashed customer sites. Cloudflare protects millions of websites from attacks. But this time, the protection system became the problem. They've since rolled back the changes and restored service. But here's what's wild: One mistake in their bot detection logic took down a massive chunk of the internet. This is the danger of centralization at scale. When one company controls so much infrastructure, a single bug becomes everyone's crisis. Cloudflare fixed it fast. But it's a reminder that even the biggest tech giants aren't immune to catastrophic failures. Decentralized systems don't have this single point of failure. Maybe that's worth thinking about.

  • CryptoonBulk_X crypto (@CryptoonBulk_X) reported

    @AlphaMike001 @SIXR_cricket Cloudflare outage pushed this Space back 2 weeks, but @SIXR_cricket’s Space next Tuesday is still on.

  • 0xgilllee Gilmo (@0xgilllee) reported

    @defikadic @cysic_xyz ngl the CloudFlare outage is messing everything up

  • forcoderr Forcoder (@forcoderr) reported

    @securityfreax I just heard the news and @cloudflare was in an outage due to too much traffic And I think @chapa_et 's sever is on cloud flare's system Now it explains why the chapa payment gateway was not working like I spent around 2 hrs 😭 thinking it was my internet damn

  • TecolabLtd tecolab (@TecolabLtd) reported

    Cloudflare went down. Half the internet broke. Every dev froze. Every startup prayed. Just a reminder: Your code isn’t the only thing crashing today 😭 #Cloudflare

  • motorcycle_guy Keith W. Boone (@motorcycle_guy) reported

    @TracketPacer The backhoe has been engineered for longer with fewer points of failure and can usually be fixed by a single well trained mechanic, often the same as the operator. It doesn’t fail when cloudflare, aws or azure goes down.

  • ErAbhishek77 Abhishek Gupta | WEB3 (@ErAbhishek77) reported

    @YadavSurajya484 Chatgpt is down because of @cloudflare

Map Check Current Status