TLDR
- Kraken restored spot and derivatives trading on October 30 after about 60 minutes of connectivity problems.
- The issue began at 02:42 UTC and was marked resolved at 03:42 UTC.
- The website, mobile app, REST, WebSocket and FIX connections were affected.
- Some users reported failed trades and blocked withdrawals, and Kraken has not given a cause.
- Claims of $130 million in Aave exposure are unconfirmed and not linked to the outage.
Kraken restored trading on October 30 after a connectivity problem blocked some customers from its spot and derivatives markets for about an hour. The exchange’s status page showed the issue was resolved at 03:42 UTC.
Kraken Suffers Connectivity and Order Issues at 02:42 UTC, Spot and Derivatives Trading Affected; Issue Resolved by 03:42 UTC
According to Kraken’s status page, the platform began investigating connectivity and order placement issues at 02:42 UTC on October 30, affecting spot… pic.twitter.com/c4jZnNJOnR
— Wu Blockchain (@WuBlockchain) October 30, 2026
Kraken first logged the problem at 02:42 UTC. It said it was investigating trouble with connections and order placement.
A second update came at 02:55 UTC. Engineers were still working and had not found the source.
What Kraken Said Was Affected
The website and mobile app were affected. So were REST, WebSocket and FIX connections, which traders and automated systems use to talk to the exchange.
Derivatives cross-exchange transfers were also on the list. Kraken did not give a technical reason for the failure.
The exchange did not share how many orders were rejected or how many accounts were hit. It also has not said whether any customers lost money.
Customers Report Failed Trades
Several users wrote to Kraken Support on X. One user said they kept seeing error messages while trying to buy crypto during a market drop.
Another user asked why withdrawals were not working. Support said it knew about the problem and was working on a fix.
A trader named Yishi said trading and withdrawals were blocked while the exchange appeared to be in post-only mode. Access later returned.
Kraken did not confirm a platform-wide post-only restriction. It also has not said whether any transactions need more processing.
The outage followed scheduled maintenance on October 29. Kraken took its spot website and API offline at 08:01 UTC for an upgrade expected to last about 15 minutes.
That work finished at 08:17 UTC. A separate FIX API problem had been fixed earlier that morning, and Kraken did not link the October 30 outage to either event.
Claims about Aave also spread during the disruption. One analyst alleged Kraken had more than $130 million in exposure to the lending platform and asked about liquidity pressure.
That claim is unconfirmed. Nothing has shown the exposure exists or that it caused the outage.
Kraken has said its DeFi Earn product links to third-party lending protocols. An October 28 Circle case study said more than $350 million in USDC had entered the product’s vaults since launch, which counts customer deposits and not Kraken’s own exposure.
Before the outage, Kraken told customers it was watching a security incident at Binance. It has not tied the October 30 disruption to any other exchange.
Kraken’s markets are running again. The exchange has yet to explain what broke, how many customers were affected, or what changes it plans to make.
Stop guessing and start investing with confidence. KnockoutStocks gives you the AI insights, market intelligence, and stock research you need to spot opportunities, cut through the noise, and make smarter investment decisions — all in one powerful platform.
Sign up today and get 50% OFF full access to our premium stock picks.
Simply use coupon code SPECIAL50 at checkout to claim your exclusive discount.







