Solana Says Routing Failure Knocked 29% of Stake Offline

A routing failure at Solana's largest infrastructure provider temporarily knocked nearly 29% of the network's stake offline on August 12, according to a new account published by the Solana Foundation.

The Foundation says blocks continued to be produced, transactions continued to land and the affected provider recovered fully in just over 30 minutes. It presents the event as evidence that the network had enough redundancy to absorb a major infrastructure failure without stopping.

Continuity is the strongest evidence

For a proof-of-stake network, losing connectivity to validators representing almost three tenths of stake is a material event. Continued block production indicates that the remaining online stake preserved the threshold required for the chain to progress.

That distinction separates a validator-hosting disruption from a network-wide halt. The Foundation says users likely did not notice the incident, but it did not publish independent latency, failed-transaction or application-level measurements in the account reviewed by Blue Rogues.

The disclosure also says Devnet lost roughly three quarters of its stake during the same event and recovered without a coordinated restart. That is useful engineering evidence, although Devnet behavior is not a substitute for measuring mainnet user impact.

Concentration remains part of the story

Solana says the affected provider, TeraSwitch, hosted 38% of network stake in the previous year. The Foundation says it worked to bring that share below 30% before the August failure.

Reducing the concentration limited the event's blast radius. But a single routing failure still affecting nearly 29% of stake demonstrates that infrastructure diversity cannot be evaluated only by counting validators. Hosting providers, network routes, software clients and geographic dependencies can create shared failure domains behind nominally separate operators.

What would strengthen the assessment

A complete postmortem would disclose the routing failure's cause, the affected validator set, changes in block time and transaction inclusion, any RPC or application degradation and the safeguards added afterward.

Until that evidence is available, two conclusions can coexist: Solana continued producing blocks through a substantial infrastructure loss, and the event exposed how much stake remained dependent on one provider.

Sources and disclosures

Primary source: Solana Foundation, September 14, 2026. The stake percentage, continuity account and recovery time are Foundation-reported and were not independently audited by Blue Rogues.

Update note

Observed September 15, 2026 at 10:55 BRT. No independent technical postmortem was identified.