Kraken said a trading disruption was resolved at 03:42 UTC on October 30. The incident began at 02:42 UTC. The exchange reported connectivity and order-placement problems across spot and derivatives services, but did not explain the cause or say how many customers were affected.
- The incident lasted 60 minutes.
- Kraken’s status page listed problems with trading, apps, APIs and FIX connections.
- Customers reported withdrawal difficulties, but Kraken did not confirm their scope.
- No evidence linked the incident to claims about Kraken’s possible Aave exposure.
Trading access and order placement were affected
Kraken’s status page reported connectivity and order-placement problems in spot and derivatives markets. The affected services listed included the website, Kraken App, REST and WebSocket APIs, FIX connections, and derivatives cross-exchange transfers. REST and WebSocket APIs let software communicate with the exchange. FIX is a protocol trading systems use to send and receive financial-market messages.
Spot trading involves buying or selling an asset. Derivatives are contracts tied to an underlying asset. Connection problems in either market can stop customers from submitting orders, including orders to open or close positions. Kraken’s status page recorded the incident from 02:42 to 03:42 UTC, but did not say that every listed service was unavailable for the whole period.
At 02:55 UTC, Kraken said it was still investigating. The exchange marked the incident resolved at 03:42 UTC, but did not publish a technical explanation or a count of affected accounts or transactions.
Customers reported failed trades and withdrawal problems
Users on X described repeated error messages and failed attempts to trade. Some also reported trouble withdrawing funds. Kraken Support acknowledged the reports and directed users to incident updates, but the exchange did not separately confirm the extent of the withdrawal complaints or whether they had been resolved. Historical customer reports of Kraken outages do not establish the duration or impact of this incident.
Trader Yishi later said access had returned. Kraken did not say whether any withdrawals or other transactions needed follow-up. That distinction matters: customer reports show what some users experienced, but do not prove that withdrawals were unavailable to everyone.
Previous-day maintenance was not named as a cause
On October 29, Kraken carried out scheduled maintenance on spot website and API services. The work began at 08:01 UTC. Kraken warned that systems could be unavailable for about 15 minutes, then marked the maintenance complete at 08:17 UTC. Markets temporarily switched to cancel-only and post-only modes during the work.
Kraken’s October 30 incident notice did not link the disruption to the previous day’s maintenance. Without a technical explanation from the exchange, any connection between the two events would be speculation.
Market claims do not explain the outage
The disruption came amid heightened concern after a security incident at Binance. Kraken had previously said it was monitoring that incident and that its own services were operating normally at the time. No link between the Binance incident and Kraken’s later trading disruption has been established.
An unnamed analyst also claimed Kraken had more than $130 million in exposure to Aave and questioned whether that could create liquidity pressure. The figure was unconfirmed. There is no evidence of a liquidity shortfall or a link between the claim and the outage.
A Circle case study dated October 28 said more than $350 million in USDC had entered Kraken’s DeFi Earn vaults since launch. That figure covers cumulative customer deposits, not Kraken’s direct exposure or funds reported lost through Aave. Circle said the product uses Veda vaults on Ink, with independent risk managers overseeing allocations to lending protocols including Aave. The deposit figure alone does not show how much went to any one protocol or whether the market disruption affected the service.
Key questions about Kraken’s outage
-
When did Kraken record the incident?
From 02:42 to 03:42 UTC on October 30. That window does not show that every affected service was unavailable for the full hour.
-
Which services were affected?
Kraken listed its website, app, REST and WebSocket APIs, FIX connections and derivatives cross-exchange transfers, along with problems in spot and derivatives trading.
-
Did Kraken explain the technical cause?
No. The exchange said its investigation was continuing, then marked the incident resolved without sharing a cause or the number of customers affected.
-
Did Kraken confirm a withdrawal outage?
No. Customers reported withdrawal difficulties, but Kraken did not separately confirm their scope or say whether they had been resolved.
-
Does the $350 million figure show Kraken’s Aave exposure?
No. Circle reported cumulative customer deposits into Kraken’s DeFi Earn vaults since launch. The figure does not represent Kraken’s direct exposure or reported losses.
Trading access returned within the recorded incident window, but Kraken has not disclosed the technical cause or the extent of the reported withdrawal problems. Those operational details, not speculation about unrelated market events, are what customers need to assess the disruption.
