Kraken reports delayed [ticker ETH] withdrawals, tracks incident updates

Kraken is experiencing delayed withdrawals on the EETH$2,686.44▼0.34% network, according to the exchange’s status-page incident record.

The immediate operational detail is notification handling. Kraken says users can subscribe to updates about the delayed withdrawals by email and/or text message. Email alerts are sent when the incident is updated, while text messages are sent whenever Kraken creates or resolves an incident. Users seeking SMS alerts must verify their phone number.

That gives affected users a way to track the incident, but it does not establish a fix. The supplied status record describes update and resolution notifications; it does not provide a resolution time, identify a technical cause or quantify how many withdrawals or users are affected.

For traders, the documented consequence is limited to delayed Ethereum-network withdrawals from Kraken. The record does not say that deposits, trading, other assets or other Kraken services are affected. It also does not specify whether a pending withdrawal will fail, remain queued or require any action from the user.

CoinGecko lists Ethereum at $2,689.94, down 0.4% over 24 hours. That price data supplies market context only; neither the Kraken status page nor CoinGecko attributes the move to the withdrawal delay. The price and change are reported by CoinGecko.

The comparison requested with Coinbase cannot be completed from the supplied primary records: no Coinbase incident document or duration is provided. The same limitation applies to the proposed comparison with Kraken’s earlier “WMTX funding delays.” The fact sheet lists no prior events, so there is no documented duration or resolution record against which to measure consistency.

What is available is narrower but useful: Kraken has published a status entry for the delayed withdrawals and specified the notification clock. Email updates follow incident changes; SMS updates follow incident creation or resolution, subject to phone-number verification. The incident’s start time and end point remain unstated.