Solana network came within 4% of halting after routing failure

On August 12, 2026, the Solana network narrowly avoided a full freeze, coming within 4.51% of halting after a routing failure at hosting provider Teraswitch knocked 28.83% of staked SOL offline. The glitch, originating in Miami and spreading to Europe and Asia, exposed severe stake concentration risks, as a single autonomous system, AS20326, held 27.34% of the network's stake—violating the Solana Foundation's 25% safety cap. Backup systems largely failed, leaving major validators like Helius offline for the entire 33-minute incident.

Teraswitch routing failure

• ▪The Teraswitch routing failure originated at its Miami facility and spread to 12 data center sites in London, Amsterdam, Dublin, Frankfurt, Singapore, and Tokyo, while North American sites remained unaffected.
• ▪Teraswitch engineers identified the malformed route within 10 minutes and restored service at 04:16:15 UTC by removing the Miami site from the backbone, with full recovery taking 33 minutes.
• ▪A routing failure at hosting provider Teraswitch on the morning of August 12, 2026, knocked 28.83% of Solana's staked tokens offline, bringing the network within 4.51 percentage points of a full halt.

Network stake concentration risk

• ▪During the August 12, 2026 incident, 94% of the Solana stake hosted on autonomous system AS20326 went offline simultaneously.
• ▪Marinade Finance reported that four autonomous systems hold two-thirds of the stake its allocation model distributes, with one system, AS395201, accounting for 36.94%.
• ▪An additional 14.1 million staked SOL went offline during the same period across unrelated hosting providers, including latitude.sh, Limestone, Butterfly Research, and Allnodes.
• ▪A single autonomous system, AS20326, hosted 27.34% of all staked Solana tokens, exceeding the Solana Foundation Delegation Program's safety cap of 25% for a single network operator.

Validator failover system failures

• ▪Helius, Solana's second-largest validator, failed to trigger its backup systems and remained offline for the entire 33-minute disruption.
• ▪Out of 74 Solana validators measured by Marinade Finance during the outage, only three—Laine, Cogent Crypto, and Lion3d—successfully failed over and recovered cleanly.
• ▪Approximately 90 Solana validators went dark during the routing failure, losing a combined 333 SOL in rewards, which will be covered by validator bonds to protect stakers from losses.

Network halt threshold mechanics

• ▪At the peak of the August 12, 2026 incident, Solana reached 28.83% delinquency, leaving the network approximately 20 million SOL tokens away from a full freeze.
• ▪Solana stops finalizing transactions and blocks if more than one-third (33.34%) of all staked tokens on the network go delinquent or offline.

Solana uptime streak

• ▪Prior to the August 12, 2026 near-miss, Solana had maintained a 100% cluster uptime streak for approximately 30 months following its February 2024 outage.
• ▪Solana's last full network halt occurred on February 6, 2024, when a bug in the LoadedPrograms JIT cache forced validators into repeated recompilation, causing a five-hour outage.

4 sources