Solana Nearly Hits Network Halt After Routing Error Knocks
29% of Stake Offline
Solana came close to a network-wide finality halt after a routing failure at infrastructure provider Teraswitch temporarily disconnected validators representing nearly 29% of the network’s staked SOL. The incident did not stop the blockchain, but it exposed the risks created when a large amount of network stake depends on the same infrastructure provider.
What Happened?
The incident occurred on August 12, 2026, when a routing problem at Teraswitch caused around 90 Solana validators to lose connectivity.
At its peak, approximately 28.83% of Solana's staked SOL became delinquent. Solana's finality mechanism requires more than two-thirds of stake to remain active, placing the network only about 4.5 percentage points from the 33.34% threshold associated with a finality halt.
Importantly, Solana did not completely shut down. Blocks continued to be produced and transactions continued to land on the network.
A Single Routing Problem Had a Network-Wide Impact
The root cause was outside Solana's consensus code.
Reports indicate that a malformed default route originating from Teraswitch's Miami facility propagated through the provider's network, affecting infrastructure in multiple locations including Europe and Asia-Pacific.
The result was simultaneous connectivity loss for a large group of validators.
Key Incident Numbers
| Metric | Figure |
|---|---|
| Date | Aug. 12, 2026 |
| Stake affected | 28.83% |
| Validators affected | ~90 |
| Finality threshold | 33.34% delinquent stake |
| Margin to threshold | ~4.5 percentage points |
| Network fully halted? | No |
| Infrastructure provider | Teraswitch |
Transaction Finality Was Delayed
Although the chain continued producing blocks, independent network telemetry showed that the incident still had a significant operational impact.
Metrika reported that some blocks took around 30 minutes to reach finality, compared with a normal finalization time of roughly 13 seconds. Slot skips also increased sharply as affected validators were unable to participate normally.
This distinction is important: network uptime remained intact, but transaction finality performance deteriorated substantially during the incident.
Why Infrastructure Concentration Matters
The incident highlighted an important distinction between validator decentralization and infrastructure decentralization.
A blockchain may have hundreds of independent validators, but if a large portion of those validators rely on the same hosting or networking provider, one infrastructure failure can affect many validators simultaneously.
In this case, the affected Teraswitch infrastructure represented a very large share of Solana's stake. Earlier Solana Foundation reporting had identified infrastructure concentration as a risk, while the Foundation says it had already worked to reduce Teraswitch's share below 30%.
Solana Says the Network Withstood the Failure
Solana's own post-incident assessment emphasizes that the blockchain continued operating despite the infrastructure failure.
The network says the incident demonstrated that validator redundancy was sufficient to keep blocks and transactions moving even after nearly 29% of stake went offline. The Foundation also said the full infrastructure recovery took just over 30 minutes.
That does not eliminate the underlying concentration risk, but it shows that the network did not cross the threshold that would have stopped finalization.
What Caused the Routing Failure?
Teraswitch's routing configuration played a central role.
According to the technical reconstruction, a default route from Miami was propagated through a route reflector in Amsterdam after important routing attributes were stripped. Other edge routers subsequently preferred the incorrect route, disrupting connectivity to affected validator infrastructure.
The problem was subsequently corrected, allowing affected validators to reconnect.
What Does This Mean for SOL?
The incident is primarily an infrastructure-risk story, rather than evidence of a failure in Solana's consensus protocol.
For SOL investors, the key issue is whether infrastructure concentration can be reduced further and whether similar failures could be prevented through stronger routing protections and validator redundancy.
The event also demonstrates why evaluating blockchain reliability involves more than simply checking whether a chain technically went offline.
Bullish Scenario
Solana could strengthen its resilience if:
- Validator infrastructure becomes more geographically distributed.
- Stake concentration among major providers decreases.
- Backup connectivity improves.
- Routing protections prevent similar failures.
- The network continues maintaining high uptime during periods of stress.
Risk Scenario
Future incidents could become more serious if:
- Large amounts of stake remain concentrated with individual providers.
- Backup systems fail to activate.
- Multiple infrastructure providers experience simultaneous disruptions.
- Another routing or connectivity problem pushes delinquent stake beyond the finality threshold.
A future event affecting more than one-third of the network's voting stake could have a materially different impact.
What Investors Should Watch
Key indicators include:
- Validator stake concentration
- Teraswitch and other infrastructure-provider exposure
- Network finality times
- Skipped-slot rates
- Validator geographic distribution
- Backup infrastructure deployment
- SOL market reaction to future outages or disruptions
FAQ
Did Solana actually shut down?
No. Solana continued producing blocks and processing transactions during the incident. However, transaction finality was significantly delayed while a large amount of stake was offline.
How much Solana stake went offline?
Approximately 28.83% of staked SOL became delinquent during the incident, according to the reported telemetry.
What caused the problem?
A routing failure at Teraswitch, a major infrastructure provider used by Solana validators, caused widespread connectivity problems. The issue was related to network infrastructure rather than a Solana consensus-code failure.
Was Solana close to a finality halt?
Yes. The affected stake reached about 28.83%, compared with the approximately 33.34% threshold at which Solana would lose the ability to finalize transactions.
Final Take
Solana's August incident was a near-miss rather than a full network shutdown.
Nearly 29% of staked SOL temporarily went offline, bringing the network within roughly 4.5 percentage points of its finality-halt threshold. While Solana continued operating, finality delays demonstrated the practical impact of concentrated infrastructure dependencies.
The event puts greater attention on validator infrastructure diversity, stake concentration and backup connectivity as Solana continues to scale.
