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.
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.
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.
For users who need to move $ATOM urgently, Ledger’s incident notice points to its alternative-methods guide. The company lists Cosmostation and Keplr as compatible third-party interfaces that can connect to a Ledger device.
Ledger’s Keplr instructions tell users to open the Cosmos app on their device and choose Keplr’s hardware-wallet connection option. That route uses another interface to access the same blockchain account while keeping the Ledger device in the transaction flow.
The safety distinction is critical: connecting a hardware wallet is not the same as importing its recovery phrase. Ledger’s security guidance says users should never enter the phrase into a computer or smartphone and should never share it, including with Ledger.
Users who do not need to transact urgently can continue monitoring Ledger’s status page. Because the incident remains open and could change without notice, its status should be refreshed before any workaround is attempted.
