Kraken Restores Spot and Derivatives Trading After One-Hour Outage
Key Takeaways
- •Kraken's connectivity outage on October 30 lasted approximately one hour, beginning at 02:42 UTC and ending when services were confirmed restored at 03:42 UTC.
- •The disruption affected spot and derivatives trading across web, mobile, REST, WebSocket and FIX channels, stopping customers from placing or managing orders during a period of elevated market volatility.
- •Kraken has not revealed the underlying cause of the outage, how many customers were affected, or whether any trading losses resulted from the interruption.
- •The incident marked the exchange's second unplanned connectivity problem within three days, following an October 28 FIX API issue that took nearly two hours to resolve.
- •Speculation about a $130 million Kraken exposure to Aave remains unverified, and no evidence connects those rumors to the connectivity failure.

Cryptocurrency exchange Kraken restored trading services on October 30 after a widespread connectivity outage disrupted access to its spot and derivatives platforms for approximately one hour, preventing some customers from placing and managing orders.
The incident began at 02:42 UTC and affected web and mobile applications, along with the REST, WebSocket and FIX connections used by automated trading systems. The exchange confirmed at 03:42 UTC that the disruption had been resolved and that affected trading services had returned to normal operation.
The outage occurred amid heightened volatility across cryptocurrency markets, raising concerns among traders who were unable to manage open positions or execute transactions during the interruption.
Trading Platforms Disrupted for One Hour
Kraken identified connectivity problems affecting spot and derivatives trading shortly after 02:42 UTC, with customers reporting difficulties accessing the platform and submitting orders through multiple interfaces.
The disruption extended beyond the exchange's standard trading website, affecting mobile users and institutional clients who rely on API connections for order execution and account management. Those connections are central to automated trading: REST and WebSocket interfaces allow software to submit and monitor orders in real time, while FIX is a messaging standard widely used by institutions to route orders. Kraken issued an update at 02:55 UTC on its status page, the standard channel exchanges use to publish incident progress, confirming that its technical team was continuing to investigate the problem. A final update at 03:42 UTC marked the incident as resolved.
The platform also recorded a temporary disruption to cross-exchange transfers within its derivatives infrastructure, although Kraken did not establish that the connectivity failure caused a platform-wide withdrawal suspension.
For active traders, interrupted connectivity can be particularly consequential during volatile markets. Positions may remain exposed to price movements while customers are unable to submit new orders, adjust existing trades or execute risk-management strategies. Because cryptocurrency venues operate around the clock, even a one-hour interruption falls entirely within live trading hours, leaving affected customers no market close at which to regroup.
Kraken has not disclosed the underlying technical cause of the outage, the number of customers affected, or whether any trading losses resulted from the interruption.
Outage Follows Recent Operational Issues
The incident follows several recent operational disruptions. On October 28, Kraken experienced a separate FIX API connectivity problem that prevented some clients from reconnecting after scheduled maintenance. That issue lasted nearly two hours before being resolved early on October 29.
The exchange also completed scheduled maintenance across its spot and derivatives platforms on October 29, temporarily restricting order submissions while systems were verified. No connection between that work and the latest outage has been established.
Aave Exposure Rumors Remain Unverified
The disruption coincided with market speculation about an alleged $130 million exposure by Kraken to Aave, following separate concerns surrounding the decentralized lending protocol. However, no verified financial disclosures or on-chain findings have established that the reported exposure created liquidity pressure at the exchange, and there is no evidence connecting the Aave speculation to the connectivity failure.
Expansion Raises Stakes for Platform Reliability
The outage comes as Kraken continues to expand its institutional and derivatives businesses. Its parent company, Payward, recently advanced plans for perpetual futures markets regulated by the U.S. Commodity Futures Trading Commission (CFTC) on Hyperliquid, adding to the group's growing trading infrastructure. Kraken has also strengthened its position in regulated European markets, recently leading exchanges compliant with the European Union's Markets in Crypto-Assets (MiCA) regulation in spot and perpetual liquidity.
Those developments place greater importance on platform reliability as the exchange serves an expanding mix of retail, professional and institutional traders.
Kraken's affected services are operational again, but the exchange has yet to provide a technical explanation for the interruption or disclose whether additional safeguards are being implemented to prevent similar disruptions. With two unplanned connectivity incidents inside three days, those pending disclosures are the key details to watch for customers relying on the platform.