TLDR
BitMEX and Kraken are the exchanges that publicly reported Cloudflare?linked service disruptions.
- BitMEX noted degraded performance and confirmed funds were safe per a report.
- Kraken cited web and mobile connectivity issues tied to the outage per the same report.
- Major peers (Coinbase, Binance, Gemini, OKX, Bybit, Crypto.com, KuCoin) reported no impact per a media summary.
Deep Dive
1. BitMEX
BitMEX stated its front end had degraded performance during the Cloudflare incident and emphasized user funds remained safe. This aligns with coverage that tied their outage to Cloudflares internal degradation and noted on?chain systems continued working normally for transactions and API access per a media report.
If you rely on BitMEXs web UI, you may have seen errors, but API and back?end processing continued, reducing operational risk.
2. Kraken
Kraken reported connectivity issues on web and mobile directly linked to the Cloudflare outage. The coverage corroborates front?end impact rather than trading core failures, with users experiencing intermittent access problems per the report above. Separate coverage also flagged multiple crypto front?ends experiencing HTTP 500 errors during the incident per a news update.
User?facing access may have been interrupted, but the issue was tied to Cloudflares network and not Krakens custody or trade engine.
3. Others Unaffected
Several large exchanges reported no disruption during the same window (Coinbase, Binance, Gemini, OKX, Bybit, Crypto.com, KuCoin) per the summary above. Broader coverage noted front?end outages across crypto apps and explorers, but not universal exchange downtime per a market report.
Exchange impact was uneven. It highlights dependency on shared web infrastructure (CDN/DNS) rather than failures of blockchain networks or core exchange systems.
Conclusion
Confirmed exchange reports of Cloudflare?linked disruptions came from BitMEX and Kraken, while many other majors indicated normal operations. The episode underscores that front?end access can fail even when back?end trading and custody remain stable, a key operational dependency to consider.
