Kraken faces mounting service faults with no explanation as funding outages stretch on
Kraken has told customers withdrawals are delayed, its second disclosed service fault on September 8, and the exchange still has not said what broke, which assets are affected or when service will return.
The withdrawal-delay notice went up on Kraken’s status page shortly after 2 p.m. UTC on September 8. By then the board already listed 23 of the company’s 725 funding services , the deposit and withdrawal rails it tracks for each supported asset and network , as degraded. Kraken described the problem in a status page statement as “a temporary hiccup affecting withdrawals, which may be briefly delayed at this time.” It said it had identified the cause, but gave no timeline, no list of affected coins and no account of what failed.
The notice compounds a deposit pause that began September 4 across more than 20 blockchain networks, including Cosmos (ATOM), Celestia (TIA), Akash and dYdX. That incident remains open, meaning some users have spent nearly a week unable to move funds into the exchange. Whether the September 8 withdrawal problem is new or a symptom of the September 4 outage is unclear; Kraken has not said whether the two are connected.
Earlier the same day, Kraken reported that account balance histories had gone stale. Daily figures have since recovered, while hourly figures remain behind, according to reporting that carried the balance-history disclosure.
Users were discussing the delays on social platforms before Kraken acknowledged them, according to separate reporting on the exchange’s communication record. No specific posts are cited, and Kraken has given no full list of affected assets. The exchange has also logged dozens of operational incidents in the weeks before September 8, including earlier episodes involving individual tokens such as Cronos , a pattern the reporting describes rather than a single failure.
Core trading functions continued without interruption throughout. Order books, price feeds, trade execution, the website and data feeds all kept running, so customers could still trade, but not move money in or out on the affected rails.
Kraken has not commented beyond its status page. Whether its next update explains the cause, names the affected networks and links or separates the two incidents remains to be seen.
