- Following a Teraswitch routing failure, Solana barely escaped a network terminal halt. During the incident, about 28.83% of staked SOL became delinquent.
- The finality criterion of 33.34% for Solana was not met. In Europe and Asia, some ninety Solana validators went offline.
- In staking rewards, validators lost about 333 SOL. Solana’s validator infrastructure concentration hazards were made clear by the incident.
Solana came close to a complete stop in the network on August 12, 2026, because of a problem with the way data was being sent. A lot of the SOL that people had staked went offline.
The problem was connected to a mistake in the way data was being sent by the company called Teraswitch. That company is an infrastructure provider. Around 28.83% of staked SOL became delinquent during the incident, bringing Solana close to the 33.34% level where transaction finality could stop.
Solana Comes Close To Finality Halt
According to an analysis from Marinade Finance, the network reached around 86% of the stake needed to trigger a finality halt. Around 19.9 million SOL remained before the critical threshold was reached.
The problem started when a default route from Teraswitch’s Miami location was advertised without the required routing information. The route was then spread across several regions, affecting validators in Europe and Asia-Pacific.
Key locations in London, Amsterdam, Dublin, Frankfurt, Singapore, and Tokyo were among those affected. North American validators were mostly unaffected.
Around 90 Validators Went Offline
🚨NEWS: @Solana came close to halting transaction finalization today after a routing failure at infrastructure provider @Teraswitch caused 28.83% of staked SOL to go delinquent. Solana would stop finalizing transactions if more than 33.34% of its staked SOL became delinquent.… pic.twitter.com/DoLybvSMVu
— SolanaFloor (@SolanaFloor) August 12, 2026
The routing problem caused around 90 validators to go offline. Validators lost a combined 333 SOL in staking rewards during the event. Network traffic started to recover within about 10 minutes, while some operators needed up to 33 minutes to fully restore their services.
AS20326 was among the most affected networks. The Solana network has a problem. It looks after a lot of Solanas, SOL, more than a quarter of it. Something weird. About 94 percent of its stake just stopped working at the same time.
Helius, which is one of the validators for Solana, was also not working during this time.
Infrastructure Concentration Raises Concerns
The incident has renewed concerns about Solana’s validator infrastructure and the risks of having large amounts of stake connected to the same providers or data centers.
Marinade Finance said it plans to tighten its limits for stake concentration by autonomous system number (ASN) and data center. It also plans to show whether validators have hot-swap and automatic failover systems.
The event shows that Solana’s risks are not limited to software problems or network congestion. A routing failure at the infrastructure level can also affect a large amount of stake at once.
Solana Needs More Validator Diversity
Solana has avoided a major finality halt in this incident, but the event highlights the need for stronger backup systems. In comparison to the larger risk, the reward loss of 333 SOL was rather minor. The event serves as a reminder that increased infrastructure, data centers, and geographic diversity will be critical to Solana’s long-term network dependability.
Stay informed with the latest trends in Web3, blockchain innovation, and cybersecurity updates at 3verseTV
You need to login in order to Like
Leave a comment