Blockscape reports Lido validator outage and failed failover
The Ledger · · Ketju Research
Affects: Lido (protocol)
What happened
An OVH failure took Blockscape's Lido-2 cluster offline and simultaneously impaired components needed by its failover design.
What changed
Fresh Vouch and MikroTik instances restored the cluster, Blockscape compensated missed rewards, and the operator committed to test a cross-provider multi-instance Vouch design.
What did not change
The record does not establish a Lido-wide outage, slashing, key compromise, withdrawal impairment, or production deployment of the planned remediation.
Confirmed
- The incident occurred June 24, 2026 and affected Blockscape's Lido-2 cluster.
- The infrastructure failure made Vouch and MikroTik unavailable and prevented failover.
- Muted monitoring delayed normal detection.
- Fresh instances restored service.
- Blockscape says it compensated lost rewards.
Still open
- Exact duration, validator count, and missed-reward amount.
- Compensation transaction and final settlement evidence.
- Production timing for the cross-provider remediation.
What it means for an advisor
- Add the shared-infrastructure and alert-suppression failures to Lido node-operator diligence.
- Verify compensation and remediation; this operator event alone does not justify restricting Lido-wide exposure.
Sources
- [Post-Mortem] Blockscape - OVH Infrastructure Incident · Blockscape via Lido Governance ·
Version 1, published . We check this event again on . Educational research, not investment advice.