TLDR
- Solana continued producing blocks and processing transactions during the outage.
- 597 of 699 staked validators, or about 85%, continued voting.
- 28.83% of staked SOL temporarily went offline.
- Solana remained above the 33.34% threshold where finality would stop.
- Affected validators recovered within about 40 minutes and lost roughly 333 SOL in rewards.
Solana remained online after an infrastructure failure disrupted more than 100 validators and temporarily pushed 28.83% of staked SOL offline. The network continued producing blocks and processing transactions while affected validators recovered, avoiding a loss of finality even as offline stake moved close to Solana’s critical threshold.
Solana Foundation technology executive Jacob Creech said 597 of 699 staked validators, or about 85%, continued voting during the incident. The remaining validators returned within roughly 40 minutes. Solana’s official status page recorded no mainnet incident for August.
Solana Validator Outage Leaves Network Online
The disruption began after an infrastructure provider used by some Solana validators suffered a routing failure. Creech said users likely did not notice the event because blocks continued to arrive and transactions continued to settle. Validators participating in the Solana Foundation Delegation Program were also unaffected.
Marinade Finance measured the event by stake rather than validator count and found that 28.83% of staked SOL became delinquent for about 33 minutes. Solana stops finalizing transactions when delinquent stake reaches 33.34%, leaving the network about 4.51 percentage points from that level during the disruption.
The difference between roughly 90 validators identified in the routing failure and the 102 validators that stopped voting reflects separate measurements. Some validators may have stopped voting for reasons not directly tied to the same infrastructure failure, while the broader network continued operating.
Affected validators lost about 333 SOL in staking rewards. Traffic began recovering within minutes, while most affected operators returned as routing paths were restored.
Teraswitch Routing Failure Exposes Validator Concentration
The routing failure was linked to infrastructure provider Teraswitch, where a malformed default route originating from its Miami facility spread through a route reflector in Amsterdam. The problem affected sites across Europe and Asia, including London, Amsterdam, Dublin, Frankfurt, Singapore and Tokyo, while North American locations remained largely unaffected.
One autonomous system, AS20326, hosted about 118.9 million SOL, equal to roughly 27.34% of network stake. Around 94% of that stake went offline at the same time. The concentration exceeded the 25% limit used by the Solana Foundation Delegation Program for a single autonomous system.
Solana still retained enough active stake to continue finalizing transactions. Roughly 71.17% of staked SOL remained online at the lowest point, keeping voting participation above the two-thirds level required for finality.
The incident did not become a network-wide Solana outage. Solana’s public status page continued to show the mainnet as operational, with no August incident recorded.
Solana Finality Threshold Remains Key After Recovery
The recovery restored delinquent stake toward normal levels before another infrastructure failure occurred. Marinade said the event brought Solana to about 86% of the way toward the level where finality would have stopped, making validator hosting concentration a key issue following the incident.
Marinade plans to review concentration limits across autonomous systems and data centers while paying closer attention to validator failover systems. Operators that use independent infrastructure providers can reduce the chance that one routing problem removes a large share of voting stake at the same time.
Creech described the event as a “proof point for Solana’s resiliency,” while the stake data also showed how close the network moved toward losing finality. Solana remained operational throughout the failure, and affected validators returned without a halt in block production or transaction processing.
