BitMEX and Kraken experienced front-end outages for three hours on Nov. 18 due to a global Cloudflare service degradation. Cloudflare resolved the issue at 14:42 UTC after implementing fixes.
BitMEX and Kraken users lost front-end access on Nov. 18 when Cloudflare reported an internal service degradation at 11:48 UTC.
BitMEX posted on its status page that degraded performance stemmed from the Cloudflare incident. The exchange confirmed all funds remained safe. Kraken’s status page reported web and mobile connectivity issues linked to the global outage.
On-chain trading continued normally on both platforms. Backend systems processed deposits and withdrawals without delay. Traders placed orders through APIs or alternative methods where available.
Coinbase, Binance, Gemini, OKX, Bybit, Crypto.com, and KuCoin registered no incident reports. Phantom wallet stayed online. Solana SOL $141.3 24h volatility: 4.5% Market cap: $78.39 B Vol. 24h: $9.33 B front-ends such as Jupiter JUP $0.27 24h volatility: 1.5% Market cap: $881.95 M Vol. 24h: $40.09 M , Raydium RAY $1.25 24h volatility: 0.7% Market cap: $334.94 M Vol. 24h: $54.63 M , and Orca ORCA $1.24 24h volatility: 0.5% Market cap: $74.58 M Vol. 24h: $7.88 M reported no problems.
Some users noted errors on Arbiscan and DeFiLlama. Toncoin TON $1.82 24h volatility: 2.6% Market cap: $4.52 B Vol. 24h: $169.61 M trackers faced intermittent issues. These stemmed from reliance on Cloudflare hosting.
Cloudflare issued the first update at 11:48 UTC. The provider reported recovery progress by 12:21 UTC.
It identified the root cause and applied a fix by 13:09 UTC. Access and WARP services returned to normal error rates by 13:13 UTC, according to the Cloudflare status page.
Updates at 13:35 UTC and 13:58 UTC noted continued remediation on application services. The company deployed a dashboard restoration change at 14:34 UTC.
It declared the incident resolved at 14:42 UTC and shifted to monitoring. At 14:57 it reported that issues persisted but were limited to the Cloudflare dashboard, and monitoring continued.
The disruption marks the most visible Cloudflare incident affecting crypto exchanges since the provider unveiled plans for NET Dollar, a USD-backed stablecoin, on Sept. 25, 2025.
Cloudflare’s Service Scale
Cloudflare serves 24.03 million active websites, according to Backlinko data from January 2025. W3Techs reports that 19.3 percent of all websites use Cloudflare for web security as of January 2025.
Netcraft’s July 2025 survey shows Cloudflare accounts for 14.6 percent of sites it tracks, with a gain of 17.7 million sites that month.
The provider handles 81 million HTTP requests per second on average. It operates from 330 cities in over 125 countries.
During the Nov. 18 degradation, some services faced intermittent impacts. Customers observed higher-than-normal error rates at various points.
Earlier Cloud Provider Disruptions
An AWS network congestion event on Oct. 20, 2025, caused similar front-end outages across multiple crypto platforms.
At the time, Coinbase Support acknowledged customer access problems during the incident while confirming funds stayed secure.
Airlines, banks, and social media services also reported widespread issues. AWS recovered back, to baseline operations the same day.
Both incidents involved front-end outages across crypto platforms. On-chain operations continued without interruption.
Cloudflare has not yet published a root-cause analysis or detailed post-mortem for the Nov. 18 degradation.
Cloudflare recently unveiled plans for NET Dollar, a USD-backed stablecoin.
next