Is Cloudflare down?
No problems detected
If you are having issues, please submit a report below.
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.
Full Outage Map
E-mailProblems in the last 24 hours
The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Cloudflare users through our website.
-
Cloud Services (47%)
-
Domains (28%)
-
Web Tools (11%)
-
Hosting (11%)
-
E-mail (4%)
Live Outage Map
The most recent Cloudflare outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Vernon |
Domains | |
 Jewar |
Hosting | |
 Waltershausen |
Cloud Services | |
 Chicago |
Domains | |
| Lübeck |
Web Tools | |
 Salvador |
Full Outage Map
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:
-
Ajit | Dev | singhajit.com
(@Ajit5ingh) reported
Around 11:20 UTC, Cloudflare’s network started failing. Users saw error pages everywhere, including on X, ChatGPT, Spotify, Crunchyroll, and thousands more.
-
Ajit | Dev | singhajit.com
(@Ajit5ingh) reported
Around 11:20 UTC, Cloudflare’s network started failing. Users saw error pages everywhere, including on X, ChatGPT, Spotify, Crunchyroll, and thousands more.
-
runsand
(@runsand_ai) reported
Today's outage wasn't Cloudflare's fault. It was a third-party vendor issue. That's exactly the point. Centralized infrastructure creates dependency chains. One vendor fails, the entire internet fails. There's no redundancy when everyone routes through the same choke point.
-
Alderon Matt
(@Deathlyrage) reported
@zenorocha Yeah im a cloudflare customer too and wondering why im paying 100s of thousands of dollars to a company thats going down all the time.
-
Crypto 🔶 ₿N
(@Crypto_bn) reported
Cloudflare put a lot of websites including some crypto related sites down. What happened at Cloudflare yesterday? - Around 11:20 UTC, a huge portion of the internet started failing with 5xx errors. - At first, Cloudflare thought it was a DDoS attack, because traffic patterns looked abnormal. - But the real issue was internal - a config file suddenly doubled in size because duplicate entries were generated in their Bot Management system. - This oversized file broke a core proxy component that handles traffic across Cloudflare’s network. - As a result, dashboards, CDN traffic, security features - everything started failing. - Fixing the config + rolling it out globally took a few hours, and things stabilized by ~17:00 UTC. A small internal data bug → huge file → crashed a critical service → global outage.
-
Ajit | Dev | singhajit.com
(@Ajit5ingh) reported
By 11:30 UTC, engineers found massive HTTP 500 errors. The first clue: Cloudflare’s bot management system had shipped a huge config file by mistake. This file broke the traffic proxy globally.
-
🐉𝙊𝙡𝙞’ 信福爱
(@olgerd_butko) reported
Cloudflare [ $NET ] reported that a bug in its bot management system caused an outage that rendered 20% of web pages inaccessible on Tuesday. This also affected half of the world's largest websites. I dreamed about $NVIDIA stock prices jumping after the market closed. $QUBT
-
Grok
(@grok) reported
@joyfillednomads @RealAlexJones Haha, loving the Pole Position vibe! If this is about the Cloudflare outage, their official postmortem confirms it was a config file bug in bot management—overloaded entries caused crashes across sites. No signs of foul play from Reuters, NYT, or other reports. More questions?
-
runsand
(@runsand_ai) reported
Cloudflare goes down. X, Spotify, ChatGPT, Discord - all offline. Billions of users affected. Single point of failure. This is why we're building Runsand. A thread on why the future of internet infrastructure can't depend on a single company 🧵
-
David G
(@dg_512) reported
Gonna start a distributed, highly-available internet service hosting company that businesses can use to run CloudFlare on
-
Kukka de Bierguirb Häst
(@horsemankukka) reported
@TripleNickels @kmcnam1 @Cuzie13 might also be a joke related to the recent cloudflare outage, maybe suggesting that less entropy caused that. think how /dev/random is slower as /dev/urandom, less entropy could make the system boot longer. (none of the assumptions are true, but. it's a joke)
-
David Robert Lewis
(@ubuntupunk) reported
@eastdakota @Cloudflare Important to reflect on what went down and what stayed up yesterday, and can anyone handle every exception caused by a changed file permission propagation?
-
Anirban Biswas
(@anirban_faith) reported
@LinuxHandbook Cloudflare pages and workers are working fine in this outage
-
Ajit | Dev | singhajit.com
(@Ajit5ingh) reported
Around 13:05 UTC, Cloudflare devs rolled back the bad file, and services began recovering. Traffic started flowing normally again. They kept fixing downstream stuff for a while after.
-
wispem-wantex
(@wispem_wantex) reported
The Cloudflare outage is a huge blow to Rust advocacy. It's a shame this came just as people were starting to warm up to the idea of using Rust for critical software-- boom, major outage, caused by Rust. It'll take years for Rust to recover from this humiliating setback :(
-
Ruby Stibbons
(@anarchyfailed) reported
@abhijitmk @DiggingInTheDi1 Cloudflare has large fuckups multiple times a year buddy. The problem would appear to be that indians are not excellent 'in computers' or even with computers.
-
Aamhi_Mumbaikar
(@kpcoolllzzz) reported
@bunnysayzz Bc you have a negative steps.. cloudflare went down globally...
-
runsand
(@runsand_ai) reported
Cloudflare charges enterprises for protection. Runsand pays device owners to provide it. Your phone, laptop, car - idle 90% of the time. Put that compute to work. Earn tokens. Strengthen the network. Decentralized doesn't mean charitable. It means better aligned incentives.
-
Trader Abba
(@TraderAbba) reported
@TheWhiteWhaleV2 @aave it could be cloudflare issue even though they announced that they fixed everything.
-
Roland Kuhn
(@rolandkuhn) reported
So I hear that yesterday Cloudflare was down. I am pleased to conclude that my work and life is sufficiently independent of these points of failure that I didn't notice this myself.
-
Flattrade
(@Flattradein) reported
@CHANDUL40975526 Due to a global Cloudflare outage, our Website, WALL, NOVO, and InstaKYC platforms are currently inaccessible. However, all our trading platforms - Web, App, Desktop, and API - are fully functional and operating without any issues.
-
SciTech💥
(@Sci_TechC) reported
@sweet_alexis82 The server cloudflare was down generally, not just only x alone many other sites where down
-
TrustED Sol🕊️
(@0Xlove_Solana) reported
@TheWhiteWhaleV2 @aave Cloudflare issue
-
Crypto 🔶 ₿N
(@Crypto_bn) reported
Market not looking good so not a gm really. Cloudflare put a lot of websites including some crypto related sites down. What happened at Cloudflare yesterday? - Around 11:20 UTC, a huge portion of the internet started failing with 5xx errors. - At first, Cloudflare thought it was a DDoS attack, because traffic patterns looked abnormal. - But the real issue was internal - a config file suddenly doubled in size because duplicate entries were generated in their Bot Management system. - This oversized file broke a core proxy component that handles traffic across Cloudflare’s network. - As a result, dashboards, CDN traffic, security features - everything started failing. - Fixing the config + rolling it out globally took a few hours, and things stabilized by ~17:00 UTC. A small internal data bug → huge file → crashed a critical service → global outage.
-
Ajit | Dev | singhajit.com
(@Ajit5ingh) reported
The cause was not an attack, just a small software bug that ended up making a critical config file too big. That crashed part of Cloudflare’s network globally.
-
Ján Pšenák (psenakdotsk)
(@not_jpsenak) reported
@Majkat_real @ariamathfilms a company called Cloudflare which has services powering all of these and more had some of their services down which broke like half the internet
-
DR. I Hate Twltter MD
(@HateTwltt3r) reported
Just got fired from my job at cloudflare, ****, oh **** oh ****
-
Steve💙🇨🇦
(@xyster) reported
@noakmilo @GithubProjects What time did Cloudflare go down again? oopsie
-
Ján Pšenák (psenakdotsk)
(@not_jpsenak) reported
@ariamathfilms a company called Cloudflare which has services powering all of these and more had some of their services down which broke like half the internet
-
ISee you
(@ISee_ysm) reported
@Cointelegraph 🚨 Today the Internet almost collapsed — about 20% of services went offline due to a Cloudflare outage. 📦 The root cause? Not an attack, but an internal glitch in their bot-management system: a config file ballooned in size and crashed part of their infrastructure. 🤯 When your cloud infrastructure is both shield and sword — but the shield breaks if one panel is faulty. 🛠 Cloudflare apologized, promised to “learn from this,” and has already begun rolling back and tightening checks. But think: how many services would you lose if this happened again? 🌐 The fragility of a centralized network isn’t just a technical risk — it’s a systemic one.