Solana Routing Bug Pushed Network 86% Toward Losing Finality

A misconfigured default route at hosting provider Teraswitch knocked nearly 29% of staked Solana offline Wednesday. The network came within about 20 million tokens of the one-third stake threshold where Solana stops finalizing transactions.

That puts the chain 86% of the way to a full finality loss, according to Marinade Finance, the liquid staking protocol whose post-mortem on X is the basis for both the CoinDesk and Decrypt reports. Solana requires more than two-thirds of staked tokens online to finalize blocks. Cross one-third offline and the chain stops confirming transactions for everyone holding SOL.

The bad route originated at Teraswitch’s Miami facility. It spread to data centers in London, Amsterdam, Frankfurt, Singapore and Tokyo. North America stayed online. Teraswitch fixed the route in about 10 minutes and traffic was flowing again by 4:16 a.m. UTC. Most affected validators, including the large operator Helius, stayed down for the full 33 minutes because their backup systems never switched on.

Concentration is what made the incident severe. A single network operator, identified as AS2032, controlled more than a quarter of all staked tokens securing Solana. That already exceeded the network’s own prescribed safety limit. Almost all of those tokens went offline at once. Other companies lost another 14 million tokens in the same short window.

One autonomous system carrying outsized stake failed. The network’s safety margin nearly disappeared with it.

Roughly 90 validators were hit. They lost 333 SOL in rewards, a sum Marinade called relatively small and said would be covered by “validator bonds.” The incident did not result in a network outage. Neither source reports transactions reversed or affected.

Solana is a leading smart contract blockchain. Assets worth $4.3 billion are locked in DeFi protocols operating on the network. The episode is the closest the chain has come to a finality loss since a five-hour outage in February 2024.

“If delinquency had gone past a third, nothing finalizes for anyone holding SOL anywhere, and there’s no bond for that,” Marinade wrote in its explainer post. “The February 2024 halt took about five hours to restart.”

Neither source reports an official statement or remediation plan from the Solana Foundation beyond Teraswitch’s route fix. The identity of AS2032 beyond the autonomous system number is not named in either report. The exact start time of the incident is not stated; only the 4:16 a.m. UTC resolution is given.

The deeper open question is structural. A single hosting provider’s malformed route brought a major L1 to the edge of finality loss because too much stake sat behind one network operator. Teraswitch patched the route. The concentration that turned a 10-minute misconfiguration into a near-halt did not.