A single hosting provider's malformed default route took almost 29% of staked SOL offline, pushing Solana to the edge of losing finality. The incident brought the network 86% of the way to the 33% threshold for staked SOL offline — meaning just over 4% more would have triggered a halt.
What a default route does
In networking, a default route is the catch-all path for traffic that doesn't match a more specific route. When that entry is malformed, it can send data to the wrong place or drop it entirely. At one hosting provider, that glitch knocked a large chunk of Solana's validators off the network.
Validators are the machines that process transactions and maintain the blockchain. They stake SOL — the network's token — as collateral. When they go offline, the network loses the ability to reach consensus.
The math of finality
Solana needs at least two-thirds of staked SOL to agree on the state of the chain. If more than 33% of staked SOL goes offline, the network can't finalize new blocks. The outage took 29% offline, leaving the network just 4 percentage points from that cliff.
Finality is what makes transactions permanent. Without it, users can't be sure a payment or trade won't be reversed. The near-miss didn't break the chain, but it came uncomfortably close.
One provider, one point of failure
The incident highlights how a single hosting provider can become a single point of failure for a major blockchain. Solana's validator set is distributed across many operators, but if a large number of them happen to run on the same infrastructure, a routing error at that provider can take them all down at once.
The network recovered, but the episode shows how fragile the system can be. The threshold for losing finality is 33% of staked SOL offline. This outage hit 29% — 86% of the way there.
What remains unclear is whether Solana's operators will change how they choose hosting providers, or if the network will add safeguards against such concentrated failures. The next incident could be the one that crosses the line.
