Kraken restored trading on October 30 after a connectivity problem blocked some customers from its spot and derivatives markets for roughly an hour. The exchange's status page showed the issue was resolved at 03:42 UTC, one hour after it was first logged. Kraken has not disclosed what caused the disruption. The episode is a reminder of how dependent crypto trading is on continuous exchange connectivity, since both manual and automated traders need uninterrupted access to place, modify, and cancel orders.

Kraken Logged Connectivity and Order Issues at 02:42 UTC; 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 and derivatives trading. A second update arrived at 02:55 UTC, with engineers still working and no root cause identified. The status page marked the incident resolved at 03:42 UTC, one hour after the first report.

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

What Kraken Said Was Affected

The disruption touched several of the exchange's access channels. The website and mobile app were affected, along with the REST, WebSocket, and FIX connections, which traders and automated systems use to communicate with the platform. API links are the backbone of algorithmic trading, so a break in those channels can sideline strategy-driven order flow just as effectively as a website or app outage. Derivatives cross-exchange transfers were also on the list of impacted services.

Kraken did not give a technical reason for the failure. The company did not share how many orders were rejected or how many accounts were hit, and it has not said whether any customers lost money.

Customers Report Failed Trades and Blocked Withdrawals

Several users wrote to Kraken Support on X during the incident. One user said they kept seeing error messages while trying to buy crypto during a market drop — a scenario in which failed orders carry more weight, because prices are moving while access is unavailable. Another user asked why withdrawals were not working. Kraken Support said it was aware of 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. Post-only is an order-book setting that accepts only maker orders, which rest on the book rather than executing immediately. Access later returned. Kraken did not confirm a platform-wide post-only restriction, and it has not said whether any transactions still need additional processing.

Outage Followed Scheduled Maintenance and a FIX API Fix

Kraken took its spot website and API offline at 08:01 UTC on October 29 for an upgrade expected to last about 15 minutes; the work finished at 08:17 UTC. A separate FIX API problem had been fixed earlier that same morning. The exchange did not link the October 30 outage to either event. Status pages like Kraken's serve as the official timeline for such incidents, which is why traders typically watch them for both maintenance windows and root-cause updates.

Unconfirmed Claims of $130 Million Aave Exposure

Claims about Aave also spread during the disruption. One analyst alleged that Kraken had more than $130 million in exposure to the lending platform and asked about potential liquidity pressure. That claim is unconfirmed, and nothing has shown that the exposure exists or that it caused the outage. The episode shows how unverified figures can circulate during outages, when official details are scarce and traders look for explanations.

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, a figure that counts customer deposits rather than Kraken's own exposure.

Binance Security Incident Watched Before the Outage

Before the outage, Kraken told customers it was watching a security incident at Binance. The exchange has not tied the October 30 disruption to the Binance incident or to any other exchange.

Kraken's markets are running again as of publication. The company has yet to explain what caused the failure, how many customers were affected, or what changes it plans to make to prevent a repeat — the open questions traders can watch for on Kraken's status page and official channels.

Source: CoinCentral