SOL routing glitch leaves validators offline

TLDR

Solana (SOL) narrowly avoided a full network halt after a routing glitch at a major data center provider temporarily knocked a large chunk of validators offline.

1. A misconfigured internet route at Teraswitch took about 28.83% of staked SOL across roughly 90 validators offline, bringing Solana close to its finality halt threshold.
2. The incident exposed how stake is concentrated on a few infrastructure providers and autonomous systems, creating correlated outage risk despite no on-chain bug.
3. Engineers restored routing within minutes, and staking teams plan diversification and stricter limits, but users should watch future reports and validator distribution as key resilience signals.

Deep Dive

1. What Actually Went Wrong

According to Marinade Finance and several reports, a default route from Teraswitchs Miami facility was incorrectly advertised and then propagated via a route reflector in Amsterdam to sites in Europe and Asia, breaking connectivity for twelve locations including London, Frankfurt, Singapore, and Tokyo. Edge routers accepted the bogus route while core routers rejected it, leaving no usable path for affected data centers and taking their Solana validators offline.

About 28.83% of all staked SOL went delinquent during the event, with nearly 29% of network stake offline and the system within roughly 20 million SOL of the 33.34% delinquency threshold at which Solana stops finalizing transactions for everyone, as described in Marinades analysis and recaps such as Solana nearly hits network halt threshold and Decrypts routing bug coverage.

Engineers identified the malformed route within around 10 minutes and restored traffic by 4:16 a.m. UTC, but many validators remained offline for roughly 33 minutes while routing reconverged. No full halt occurred and user funds remained safe, but finality came uncomfortably close to stopping.

2. Concentration And Correlated Risk

Marinades stake breakdown shows the outage was heavily concentrated on one autonomous system, AS20326, which carried about 118.9 million SOL, or 27.34% of total staked SOL, above the Solana Foundations informal 25% cap. Roughly 94% of that stake went dark simultaneously, with an extra 14.1 million SOL offline across other hosting providers, as detailed in The Defiants delinquency report and CoinDesks incident summary.

Marinade noted that four autonomous systems together hold about two thirds of the stake its allocator manages, with one ASN alone around 36.94%. This means that infrastructure-level problems at a single provider or AS can rapidly push the network toward a superminority losing finality, even when the underlying blockchain software is healthy.

The episode echoes Solanas five-hour finality outage in February 2024, but here the trigger was off-chain networking rather than a client bug, highlighting how decentralization must cover hosting and connectivity, not just validator count.

3. Fixes, Follow-Ups, And What To Watch

Teraswitch is preparing a full postmortem and continues to investigate whether the defect lay in Miami edge routers or the Amsterdam route reflector, after issuing an initial explanation of the routing fault in the backbone, as noted in The Defiants coverage. Marinade has said it will review and tighten stake concentration limits by autonomous system and data center and disclose validator failover capabilities.

On Solanas side, broader efforts such as the upcoming Firedancer client, performance upgrades, and governance debates around validator economics are already in motion, but this incident adds pressure to push operators toward better failover, multi-region setups, and less dependence on single ASN or provider clusters.

For everyday users and investors, the practical signals to watch are: stake distribution across validators and hosting providers; whether future incidents show faster failover and recovery; and how governance and staking services respond with diversification policies.

Conclusion

Solanas routing glitch shows that off-chain infrastructure problems can nearly halt a high-throughput blockchain even when the protocol itself is sound. The network escaped with a short validator outage and lost rewards, but the episode exposed heavy stake concentration on a small set of providers and autonomous systems. Going forward, Solanas robustness will depend not just on client upgrades and tokenomics, but on whether validators and staking platforms diversify connectivity and enforce real limits on correlated infrastructure risk.