Kraken reports stuck withdrawals as funding problems hit 23 services

Kraken is dealing with a messy stretch of operational turbulence. The exchange announced on September 8 that users were experiencing withdrawal delays tied to funding issues across 23 of its services, compounding a deposit freeze that had already been running since September 4.

That earlier pause affected more than 20 blockchain networks, meaning some users spent the better part of a week unable to move funds in or out of the platform.

What actually broke

Kraken’s status page flagged degraded performance across its funding infrastructure, though the exchange stopped short of publishing a full list of affected assets or a concrete resolution timeline. Among the networks confirmed as impacted: Akash, Cosmos, Celestia, and dYdX.

Core trading functions kept running. Order books, price feeds, and trade execution continued without interruption, so active traders could still do their thing even if they couldn’t get money into or out of the exchange.

A pattern of operational headaches

This isn’t Kraken’s first rodeo with funding disruptions. The exchange has logged dozens of operational incidents in the weeks leading up to the September 8 announcement, and prior episodes involving specific tokens, including Cronos, have surfaced before.

Kraken hasn’t offered enough transparency on timelines and affected asset lists, and users on social platforms began flagging the delays before any official acknowledgment arrived.

The IPO ambition hanging in the background

Kraken’s parent company, Payward, has been making moves toward deeper integration with traditional finance. That includes ambitions around tokenized assets and connectivity to established venues like Nasdaq and the London Stock Exchange, as well as ongoing conversations around a potential initial public offering.

The 23 affected services represent a non-trivial slice of Kraken’s funding infrastructure, broad enough that users across a wide range of assets and networks were caught in the disruption. Until the full list is published and services are confirmed restored, the operational picture remains incomplete.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.