Kraken Acknowledges Connection and Order Problems Across Its Services

Kraken acknowledged reports of connection failures and order-submission problems across its web, mobile and API services on Oct. 30, disrupting user access as separate concerns about Aave-linked exposure circulated without confirmation.

Users described two problems: reaching the exchange and submitting orders. Reports covered Kraken's website, mobile service and application programming interface (API), indicating the issue affected multiple ways users connect to the platform.

That spread matters because the same reports involved both access and trade submission, putting basic platform use and order entry in the same incident account.

Separately, a market analyst speculated that a temporary pause in Aave markets could leave Kraken vulnerable to liquidity pressure, citing more than $130 million in related exposure. No liquidity crisis was confirmed, and the speculation does not show that the Aave pause caused Kraken's connection or order problems.

Kraken's service issue and the Aave exposure theory remain distinct: one describes reported technical problems, while the other is an unconfirmed concern about liquidity.