Live  /  Ledger  /  Incident

Ledger: Blast (BLAST) Mainnet Degraded Service

Ledger · ledger.comMajor incidentResolved2026-10-30 04:36 UTC
Public — what happened

Summary

Ledger said it was having technical problems with the Blast Mainnet inside Ledger Wallet, which it rated as a major incident. The company said users might be unable to send transactions, add accounts, or see their balances and transaction history. It reported the problem beginning at 17:08 UTC on October 29, 2026, said its team was working on it, and pointed people with urgent transactions to a support article for other options. The incident is marked resolved as of 04:36 on October 30, though the company did not give a cause in the text provided.

Affected

Blast (BLAST)

As listed on Ledger’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Ledger against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Ledger: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Ledger report →

More from Ledger

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Ledger status & history page.

Related: Ledger status & history. SquidGrid is not affiliated with Ledger.