Kraken has resolved 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.
Summary
- Kraken reported connectivity and order placement problems affecting spot and derivatives trading on October 30.
- The disruption began at 02:42 UTC and was resolved at 03:42 UTC, according to the exchange’s official status page.
- Website, mobile, REST, WebSocket and FIX connections were among the affected services.
- Some customers reported being unable to trade or withdraw funds, while others encountered error messages.
- Separate speculation about more than $130 million in alleged Aave exposure remains unconfirmed, with no established link to the outage.
According to Kraken’s official status page, the exchange began investigating connectivity and order placement problems at 02:42 UTC, affecting its website, mobile applications and several trading interfaces. The company issued another update at 02:55 UTC before confirming that the incident had been resolved at 03:42 UTC.
Meanwhile, the disruption prompted complaints from customers who reported being unable to trade or access certain account functions. It occurred during heightened concern across cryptocurrency markets following the major security incident at Binance, although Kraken has not identified a cause or connected its service problems to another exchange.
Kraken confirms trading problems across multiple services
Kraken’s initial notice identified problems affecting both spot and derivatives customers attempting to connect to the platform or submit orders. The affected connections included REST, WebSocket and Financial Information Exchange (FIX), which traders and automated systems use to communicate with the exchange.
The notice covered regular customers using Kraken’s website or mobile applications alongside traders who connect through automated trading software.
During the disruption, customers could encounter difficulties accessing markets or submitting orders, including orders intended to open or close positions. Kraken did not publish a count of rejected transactions or affected accounts.
At 02:55 UTC, the company said its investigation was continuing without identifying the source of the problems. Its subsequent 03:42 UTC update confirmed that the incident had been resolved, establishing a 60-minute interval between the initial notice and resolution.
The incident report listed the website, Kraken App, REST and WebSocket APIs, and derivatives cross-exchange transfers among the affected components. It did not provide a technical explanation of the failure.
Kraken users report failed trades and withdrawal difficulties
As the problems unfolded, several customers contacted Kraken’s support account on X seeking information about their accounts.
One user, posting under the name urmom.eth, complained about receiving repeated error messages while attempting to buy cryptocurrency during a market decline.
Kraken Support acknowledged the issue, directing the customer to its incident page for updates while engineers investigated the problem.
Another user, CryptoRhino, questioned why withdrawals were unavailable. The support team responded that it was aware of the reported problem and was working on a resolution.
Separately, cryptocurrency trader Yishi reported being unable to trade or withdraw funds while the exchange appeared to be operating in post-only mode. The trader later said access had returned.
Post-only trading allows users to submit qualifying limit orders that add liquidity to an exchange’s order book. It generally prevents orders from immediately executing against existing orders, although Kraken did not confirm that a platform-wide post-only restriction formed part of the October 30 incident.
Kraken has not published a separate assessment of the reported withdrawal difficulties or stated whether any customer transactions require further processing.
Kraken outage follows scheduled exchange maintenance
The interruption followed several operational updates involving Kraken’s trading infrastructure.
On October 29, the exchange carried out scheduled maintenance affecting its spot website and API services at 08:01 UTC. Kraken had warned customers that the systems could become unavailable for approximately 15 minutes during the upgrade.
Its maintenance records show that markets temporarily entered cancel-only and post-only modes while engineers checked system status. The scheduled work finished at 08:17 UTC.
Derivatives platform maintenance took place during the same period, while a separate FIX API connectivity problem had been resolved earlier that morning.
Kraken’s October 30 incident notice did not attribute the latest disruption to the previous day’s maintenance.
Aave exposure claims emerge during Kraken disruption
The trading problems coincided with unconfirmed claims about Kraken’s exposure to decentralized lending platform Aave following the suspension of some Aave markets during the wider cryptocurrency market disruption.
One analyst cited alleged exposure exceeding $130 million and questioned whether the exchange could face liquidity pressure. However, the claim did not establish that Kraken was experiencing a liquidity shortage or that the alleged exposure caused its connectivity problems.
Kraken has previously disclosed links between its DeFi Earn product and third-party lending protocols. In an October 28 case study, Circle reported that more than $350 million in USDC had entered Kraken’s DeFi Earn vaults since launch.
The study explained that the service uses Veda vaults on Ink, with independent risk managers overseeing allocations to lending protocols, including Aave.
Circle’s figures describe cumulative customer deposits into the product, not Kraken’s direct financial exposure or an amount lost through Aave.
Before the disruption, Kraken had assured customers that it was monitoring the Binance security incident and that its services were operating normally at the time of that statement. Its later official incident report recorded the October 30 trading problems as resolved at 03:42 UTC.
Elsewhere, crypto.news recently reported Kraken’s stablecoin growth following its partnership with Circle, including increased USDC balances and activity involving decentralized lending products.
