Wednesday, September 16, 2026

Creating liberating content

CoinEx quits after 9...

Crypto exchange CoinEx is shutting down after nine years, citing shrinking revenue and...

Bitcoin, BTC-Related Stocks Tumble...

Bitcoin’s price tumbled — along with crypto-related stocks — following the blockage of...

Bitcoin Core v32 RC1:...

Bitcoin Core v32.0rc1 has turned the Sept. 14–Oct. 10 window into a concentrated...

AI Could Be Bitcoin’s...

Artificial intelligence may turn out to be an unexpected driver of...

Ledger ATOM outage persists after Cosmos Hub recovery

Ledger’s status page continued to list Cosmos (ATOM) as a major outage on Sept. 13, leaving users unable to view ATOM balances or transaction history and unable to submit transactions through Ledger Wallet more than four days after the incident began.

The company opened the incident at 19:41 CEST on Sept. 8. As of press time, its latest update, posted at 16:12 CEST on Sept. 10, said restoration work was continuing and that the affected features remained unavailable. Ledger has not disclosed a cause or an estimated restoration time.

The continuing warning does not mean Cosmos Hub is still halted. It shows that Ledger Wallet’s service path for retrieving account data and sending ATOM transactions has not recovered with the network itself.

Cosmos Hub recovered before Ledger Wallet

QuickNode reported that Cosmos Mainnet stalled at block 32,878,318 at 18:12 UTC on Sept. 8. The infrastructure provider said its nodes had returned to the chain tip by 14:26 UTC on Sept. 9, then marked its incident resolved at 00:24 UTC on Sept. 12.

Read More:  Crypto ETFs appeared to hit $10B in hours, but filing data exposes where that money really came from

The Cosmos Hub RPC endpoint was above block 32.9 million on Sept. 12 and reported that the node was not catching up. That placed the chain tens of thousands of blocks beyond the height in QuickNode’s initial alert.

Related Reading

Major v17 update causes 4-hour Cosmos Hub downtime, ATOM token stable

Together, those readings separate two layers of the problem. Cosmos Hub resumed producing blocks, while Ledger Wallet access remained unavailable. Users may therefore see missing balances or history in Ledger Wallet even though the network is processing new blocks.

QuickNode’s resolution applies to its infrastructure, while Ledger’s separate incident remains identified. Those states can coexist because a wallet interface can stay unavailable after network nodes have caught up. Ledger has not said which part of its service path is responsible.

Read More:  Thailand stablecoin proposal limits third-party transfers