Solana Nears Halt as 28.83% of Staked SOL Goes Offline

Solana’s validator network came within 4.51 percentage points of a full transaction-finality halt on Wednesday, August 12, after a routing failure at infrastructure provider Teraswitch knocked 28.83% of all staked SOL offline. The incident pushed the network to 86% of the critical 33.34% delinquency threshold, the point at which Solana’s protocol stops finalizing transactions entirely. Blocks kept producing throughout, and user funds remained secure, but the 33-minute disruption exposed concentration risk that the network’s own delegation policies were designed to prevent.

A Routing Error Cascaded Across Continents

The fault originated at Teraswitch’s Miami facility, where a default route was advertised without proper network attributes. A route reflector in Amsterdam then propagated the malformed route across the provider’s backbone, cutting off connectivity at 12 data center sites spanning London, Amsterdam, Dublin, Frankfurt, Singapore, and Tokyo. Teraswitch confirmed that customers at those specific locations lost reachability both to the broader internet and to internal backbone destinations between affected sites; North American facilities were unaffected throughout.

The disruption’s severity traced to a single point of concentration. Autonomous system AS20326, which hosts more than a quarter of all staked SOL, roughly 118.9 million tokens, saw 94% of that stake go dark simultaneously. That concentration sits at 27.34% of total network stake, above the 25% cap per autonomous system recommended under the Solana Foundation Delegation Program. Staking platform Marinade Finance, which published the incident analysis, calculated the network had roughly 20 million SOL of active stake standing between it and a full finality freeze.

Recovery Came Fast, But Failover Tools Underperformed

Teraswitch engineers identified the malformed route within approximately 10 minutes and removed the Miami site from the company’s backbone, with full traffic restoration logged at 04:16:15 UTC, about 33 minutes after the disruption began. Of 74 tracked validators, only three automatically switched to backup locations during the outage; major operators, including Helius, remained offline for the entire window rather than failing over. Roughly 90 validators were affected in total, collectively missing 333 SOL, worth approximately $25,600, in staking rewards that validator bond programs are set to cover at the close of the current epoch.

Solana Foundation VP of Technology Jacob Creech confirmed rapid recovery on social media, noting that validators managed directly under the Solana Foundation Delegation Program remained unaffected throughout the incident. Teraswitch has since said it will revise its stake-concentration limits by network and by data center, and begin disclosing which validators operate with hot-swap and automatic failover capability, information not currently verifiable from outside the company.

• Solana’s last full network halt occurred February 6, 2024, and lasted approximately five hours; Wednesday’s incident never stopped block production
• The network’s official status page continues to show 100% uptime over the trailing 90 days, since finality delinquency is tracked separately from block production halts

Conclusion

Solana’s chain kept producing blocks throughout Wednesday’s incident, and the network’s 30-month streak without a full halt technically remains intact, but the near-miss revealed that a single infrastructure provider’s routing error came within roughly 4.5 percentage points of freezing transaction finality for every SOL holder. The event lands as the network prepares for its Alpenglow consensus upgrade, targeting sub-second finality and due by October, which is designed in part to reduce exactly this kind of systemic exposure. Whether the Solana Foundation tightens its delegation caps in response, or leaves enforcement to individual infrastructure providers like Teraswitch, will determine whether Wednesday’s close call becomes a genuine catalyst for decentralization or simply a warning that goes unheeded until the next routing failure tests the threshold again.