Kraken Withdrawal Delays and Multi-Chain Deposit Suspension
On Tuesday, Kraken informed customers of withdrawal issues, stating that the cause has been identified but no timeline for resolution has been provided. The official status page describes it as a temporary fault, with trading, website, and market data interfaces still operational.
This is the second public fault reported on the same day. Hours earlier, account balance historical data experienced delays, which were later marked as resolved; the withdrawal blockage incident was also separately recorded on the status aggregation page, with some entries later rewritten as processed, but the overall funding channel remains degraded.
A broader fault has persisted since September 4. The official incident page states that deposits for networks including Akash, Babylon, Celestia, Cosmos Hub, Coreum, dYdX, Dymension, Fetch.ai, Initia, Injective, Juno, Kava, MANTRA, Neutron, Nym, Osmosis, Saga, Secret Network, Sei EVM, Stride, Terra, and Terra Classic have been suspended, with withdrawals possibly unavailable or delayed. Celestia and Cosmos remain on the list of networks that have not been shut down.
The status page shows that out of 725 funding services, 23 are degraded, with the damage concentrated on cryptocurrency deposit channels rather than the matching engine. Meanwhile, the Cronos funding gateway was under investigation from the end of August until September 8, when it was declared resolved; Kaspa withdrawals and PEAQ deposits also experienced separate delays in the preceding days. The exchange has not published a complete list of affected assets and has not committed to the order of recovery for each chain.
The parallel arrangement is that 21 tokens will stop trading and deposits at 14:00 UTC on September 11, with the withdrawal window remaining open until December 10, and remaining balances expected to be forcibly disposed of between December 14 and 18, including Cosmos ecosystem assets like JUNO that overlap with this deposit suspension. Users who encounter both deposit suspensions and imminent delistings will have their on-chain migration window compressed.
Mechanically, this is a liquidity freeze driven by operational incidents, not a price shock. Being able to trade but not deposit or withdraw effectively locks positions in the platform's internal order book. Beneficiaries are competitors with open deposit and withdrawal channels and over-the-counter market makers; those under pressure are Cosmos ecosystem holders needing to withdraw small tokens before delisting, and arbitrageurs relying on Kraken as a fiat/cross-chain hub. Funds are temporarily unable to leave custody, shifting risk from market prices to counterparties and operational timeliness.
In the past 30 days, there have been about 37 official incident records, with several still unresolved. Cryptocurrency funding components are marked as slower than normal, and the status monitoring site rates the overall status as degraded rather than a complete outage.
Source: Public Information
ABAB AI Insight
Kraken has long differentiated itself by its compliance licenses and relatively conservative asset listings, but its funding gateways have always been a shortcoming: single-chain gateways, Cosmos SDK application chains, and EVM sidechains operate independently, and any delay in validation or signing can split into dozens of "Funding" sub-items on the status page. The recent consecutive reports of issues with Cronos, Kaspa, and PEAQ indicate that the problem is not sporadic congestion, but rather the capacity limits of multi-chain entry layers during parallel maintenance.
The capital path is custodial sedimentation. While trading continues, the platform can still collect transaction fees, but external redemptions are delayed, effectively keeping customer assets in hot wallets and cold layers for a few more days. For exchanges pushing stock tokens, fiat channels, and institutional custody, this "temporarily unable to leave" funding serves as both a liquidity buffer and a sensitive exposure for regulation and auditing—once it overlaps with the delisting liquidation window, forced sales could turn operational incidents into price shocks.
A comparable situation is the repeated occurrence of "trading normal, withdrawals queuing" seen in various exchanges post-2022: the extreme version of redemption blockage before the FTX collapse, and Binance and Coinbase have also frequently labeled issues as status incidents during network upgrades or on-chain congestion. Kraken is currently experiencing operational mismatches during its expansion phase: its product line extends to securities, derivatives, and payment cards, while its deposit infrastructure still connects one public chain at a time, and has not yet completed a unified settlement layer.
The structural judgment points to a custodial bottleneck in the restructuring of the industry chain. The suspension of multi-chain deposits reveals not the fundamentals of a specific token, but that exchanges treat "supporting a new chain" as a marketing item and consider withdrawal security as a post-fact patch. When Cosmos-like application chains share the same signature and scanning pipeline, a single point of failure can spread throughout the ecosystem; pricing power shifts from on-chain block confirmations to the centralized status page's "Identified / Monitoring" wording.
ABAB News · Cognitive Laws
Trading is possible but withdrawals are not, shifting risk from price to counterparties.
New multi-chain support is marketing; withdrawal recovery is the balance sheet.
When the status page indicates degradation, liquidity has already unilaterally closed its doors.