Live  /  Providers  /  Ledger

Ledger

ledger.comReporting incidents

Independent assessment — SquidGrid is not affiliated with Ledger. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Crypto & trading · SquidGrid tracks Ledger’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Ledger is reporting

Current & recent incidents

identified

Stellar (XLM) Mainnet Degraded Service

Minor impact · 2026-07-31 12:51 UTC · still open per the provider’s page — may be stale

Resolved

Ledger Recover Service Disruption

Critical impact · 2026-09-25 09:33 UTC

Resolved

Ledger Recover service degradation

Critical impact · 2026-09-25 08:57 UTC

Resolved

Elrond (EGLD) Mainnet Service Disruption

Critical impact · 2026-09-25 06:10 UTC

Resolved

Cosmos (ATOM) Mainnet Service Disruption

Critical impact · 2026-09-23 12:33 UTC

Resolved

Binance (BNB) Mainnet Degraded Service

Major impact · 2026-09-22 07:09 UTC

Resolved

Binance (BNB) Mainnet Service Disruption

Critical impact · 2026-09-22 05:47 UTC

Resolved

Near Protocol (NEAR) Mainnet Service Disruption

Critical impact · 2026-09-22 01:05 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what Ledger has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Ledger runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Ledger is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Ledger.