Kraken Restores Trading After One-Hour Platform Outage

Cryptocurrency exchange Kraken experienced a trading disruption that prevented some customers from accessing its platform and submitting orders across spot and derivatives markets for approximately one hour on October 30, according to CryptoNews.

The disruption began at 02:42 UTC and was resolved at 03:42 UTC, as confirmed by the exchange’s official status page. The technical issues affected website, mobile, REST, WebSocket, and FIX connections. During the window, several customers reported being unable to trade or withdraw funds, alongside encountering recurring error messages when attempting to execute transactions.

Technical Impact Across Services

Kraken’s initial notices confirmed that connectivity and order placement problems impacted both spot and derivatives customers. The failure affected standard users accessing the exchange via its website and mobile applications, as well as automated traders utilizing REST, WebSocket, and Financial Information Exchange (FIX) APIs.

As engineers investigated the source of the disruption, the company issued status updates at 02:55 UTC before confirming a full resolution at 03:42 UTC. The platform did not publish a technical explanation for the failure or provide figures regarding rejected transactions and affected account numbers.

Unconfirmed Exposure Claims

During the platform disruption, separate claims emerged regarding Kraken's exposure to decentralized lending platform Aave following market-wide volatility and the suspension of certain Aave markets. One analyst cited alleged exposure exceeding $130 million and questioned potential liquidity pressure on the exchange. However, the report noted that these claims remained unconfirmed and no established link tied the alleged Aave exposure to Kraken's connectivity outage.

Key facts

• Kraken experienced a trading outage lasting for approximately one hour on October 30.
• The disruption started at 02:42 UTC and was resolved at 03:42 UTC, according to the official status page.
• Affected services included the website, mobile applications, REST, WebSocket, and FIX connections across spot and derivatives markets.
• Unconfirmed claims emerged regarding more than $130 million in alleged Aave exposure during the incident.