A global network outage at Cloudflare on Tuesday caused major disruptions across the crypto industry, knocking several leading exchanges and Web3 platforms offline and triggering error messages across the wider internet.
Cloudflare, whose network infrastructure supports millions of websites with security, traffic routing, and edge computing, confirmed the issue late Tuesday morning UTC. The company described the incident as an internal service degradation affecting multiple parts of its global network. While Cloudflare has identified the cause and begun rolling out a fix, the company warned that elevated error rates may continue as systems recover.
Crypto front-ends hit across the board
The outage triggered waves of “500 Internal Server Error” messages on key crypto services. Coinbase and Kraken were among the exchanges affected, while Etherscan, Aave, and analytics platform DeFiLlama also reported front-end disruptions. The impact spread beyond Web3. Elon Musk’s X was among the major Web2 sites showing intermittent issues.
Cloudflare shares slipped roughly 3.5 percent in pre-market trading following the news.
The incident came during scheduled maintenance at several Cloudflare data centers, though the company has not confirmed any connection between the maintenance and the outage. Full details on the root cause are still pending.
A recurring challenge for the crypto ecosystem
This is not the first time Cloudflare outages have reverberated through the crypto sector. Major disruptions in June 2022 and July 2019 similarly brought exchanges and analytics platforms offline. Broader Web2 infrastructure problems have also created headaches for crypto platforms in recent years. AWS and Microsoft outages, as well as last year’s widespread CrowdStrike software failure, led to issues across wallets, exchanges, and applications. In each case, however, underlying blockchain networks continued to operate normally.
John Biggs
The recurring nature of these outages has pushed industry leaders to highlight the risks of overreliance on a small number of infrastructure providers.
David Schwed, COO of SovereignAI, said the latest incident is a reminder that organizations must assume outages will happen and prepare accordingly.
“If your organization needs to be up 24/7, you have to build your infrastructure assuming these outages will happen. A business continuity plan comprised of ‘wait for vendor to restore’ is pure negligence,” he said.
