Solana's blockchain continued producing blocks and processing transactions even when a single infrastructure provider's failure took roughly 27% of its staked validators offline on August 12, 2026. The incident, which lasted about 33 minutes, tested whether the network's distributed validator architecture could withstand a concentrated infrastructure failure. It passed the test, but only narrowly, exposing a concentration risk that experts say should concern the community.

What Happened During the Teraswitch Outage?

Early on August 12, 2026, Teraswitch, a data center and network provider, experienced a routing failure that disrupted several of its international sites. The failure affected validators hosted on Teraswitch's infrastructure, which collectively held a significant portion of Solana's staked SOL (the network's native cryptocurrency). Within about 10 minutes, Teraswitch engineers identified the fault, and service was fully restored roughly 33 minutes after the failure began.

During the outage, 597 of Solana's 699 staked validators continued voting and maintaining network consensus. However, 102 staked validators stopped voting, and approximately 28.83% of all staked SOL became delinquent, meaning those tokens temporarily stopped participating in the network's consensus process.

How Close Did Solana Come to a Network Halt?

Solana's consensus mechanism requires that at least 66.66% of staked tokens remain active to finalize transactions. If delinquency reaches 33.34%, the network stops finalizing new blocks. During the Teraswitch outage, delinquency hit 28.83%, leaving only a 4.51 percentage point margin before the network would have halted.

The reason the network came so close to this threshold reveals a deeper concentration problem. Teraswitch's autonomous system (identified as AS20326) held 27.34% of all staked SOL, above the Solana Foundation's own recommended 25% cap for how much stake a single network operator should control. When Teraswitch went offline, roughly 94% of that operator's stake went offline simultaneously, accounting for close to 89% of the incident's total delinquent stake.

"Last night an infrastructure provider used by some Solana validators had a failure. You probably didn't notice, because the network didn't: blocks kept producing and transactions kept landing," said Jacob Creech, Vice President of Technology at the Solana Foundation.

Jacob Creech, Vice President of Technology, Solana Foundation

Why Infrastructure Diversity Saved the Network

Solana's validators run across multiple independent infrastructure providers rather than relying on a single shared system. When Teraswitch's routing broke, validators hosted elsewhere continued operating normally, allowing the network to maintain consensus and block production. This distributed approach prevented a complete network failure, even though the concentration of stake behind Teraswitch created significant risk.

Marinade Finance, a Solana liquid staking protocol that tracks validator infrastructure, flagged the concentration issue publicly during the incident. The protocol noted that the stake concentration at Teraswitch exceeded the Solana Foundation's own safety guidelines and that similar concentration risks exist across other network operators, including Marinade's own stake allocation.

How to Reduce Infrastructure Risk in Blockchain Networks

• Enforce Stake Concentration Limits: Implement and enforce caps on how much staked cryptocurrency a single infrastructure provider can control, similar to the Solana Foundation's 25% guideline, to prevent any single provider failure from threatening network consensus.
• Diversify Validator Hosting: Encourage validators to distribute their infrastructure across multiple independent data centers and network providers rather than consolidating on a single platform for cost or convenience reasons.
• Monitor Real-Time Concentration Metrics: Develop transparent, real-time dashboards that track stake concentration by infrastructure provider so the community can identify emerging risks before they become critical.
• Establish Provider Redundancy Requirements: Require validators to maintain backup infrastructure or failover mechanisms so that a single provider's outage does not immediately take a validator offline.

What Does This Mean for Solana's Long-Term Infrastructure Health?

Solana's validator count has been declining steadily. The network's 7-day moving average of daily validators stood at around 691 as of August 13, 2026, down from more than 750 validators in May 2026 and significantly below the network's 2023 peak. Fewer validators can mean less geographic and infrastructure diversity, which increases the risk that a single provider failure could push the network closer to halting.

The Teraswitch incident also highlighted a broader challenge: as blockchain networks grow, they often become more dependent on a handful of large infrastructure providers for cost and operational efficiency. This creates a tension between decentralization ideals and practical infrastructure economics. The Solana Foundation's validator support programs, including the Solana Foundation Delegation Program, aim to encourage validator participation and infrastructure diversity, but the August 12 incident shows that concentration risks persist despite these efforts.

Beyond validator infrastructure, Solana's ecosystem is expanding into other critical services. MoneyGram, the global payments company, recently became a Solana validator and launched MoneyGram Ramps, a service enabling cash-to-crypto and crypto-to-cash transfers through Solana applications. This move signals that major financial institutions are integrating deeper into Solana's infrastructure, which could further diversify the network's operational base.

The August 12 outage serves as a reminder that blockchain networks, despite their decentralized design, depend on real-world infrastructure that can fail. Solana's network survived this time because most validators were not sitting behind the failed provider. As the network evolves, maintaining genuine infrastructure diversity and monitoring concentration risks will be critical to preventing a future incident from causing a network halt.