Teraswitch Routing Failure Brought Solana Within 4.5 Points of a Finality Halt

A routing failure at Teraswitch, a hosting provider used by Solana validators across Europe and Asia-Pacific, knocked roughly 90 validators offline for approximately 33 minutes on August 12, sending 28.83% of all staked SOL into delinquent status. Solana's Tower Byzantine Fault Tolerance consensus requires more than 66.67% of staked SOL to participate actively to finalize transactions, placing the network 4.5 percentage points from the threshold at which blocks stop becoming permanent. The network recovered in full. Finality was never interrupted.

What Went Wrong: Teraswitch and the 90 Validators That Went Dark

At 07:46 UTC, Triton One Triton One reported that "one of our infrastructure providers had a major network outage this morning," adding that it had rerouted traffic to available capacity during the incident and that service was restored. SolanaFloor identified Teraswitch as the provider, tagging the company directly in its report on the event.

The routing failure took down around 90 validators hosted at Teraswitch data centers in Europe and Asia-Pacific. Those validators stopped voting in consensus, and their combined stake weight registered as delinquent. Marinade MNDE$0.019+3.6% Marinade Finance data, cited by SolanaFloor, shows the affected validators collectively missed approximately 333 SOL in staking rewards across the 33-minute outage.

Triton One said it will publish further detail once it receives a postmortem from Teraswitch and completes its own review.

The 33.34% Threshold: What Tower BFT Requires

Solana's consensus is built around a supermajority. Tower BFT requires that validators controlling more than two-thirds of all staked SOL — 66.67% — participate in voting for a block to be finalized. Cross the mirror threshold in the other direction, and if validators holding more than 33.34% of stake go delinquent simultaneously, the network loses the ability to stamp blocks as irreversible.

At peak delinquency, 28.83% of staked SOL was offline.

Blocks continued to be produced throughout. What was at risk was finality, the property that makes a confirmed transaction permanent rather than theoretically reversible. The gap between 28.83% and 33.34% was real but not wide enough to tip the network over.

Solana does not slash validators for downtime. A validator that goes delinquent stops earning rewards; stakers delegated to that validator receive proportionally lower returns for the epoch. That is the full financial consequence for delegators.

Infrastructure Concentration as the Structural Problem

Individual validator failures are routine on Solana: hardware issues, software misconfigurations, network connectivity gaps. What distinguished this incident was simultaneity. Roughly 90 validators went down at the same moment because they shared a single network path.

Coinbase's Q2 2026 Solana Validator Performance Report noted that splitting validator deployments across multiple providers limits the blast radius of a single-provider outage. The Teraswitch failure put that logic in concrete terms: validators distributed across multiple operator identities but concentrated at one hosting provider behaved as a single point of failure when the routing failed.

Solana had completed 30 consecutive months without a network-wide outage as of August 10 — a milestone that counts full halts, where block production itself stops. The Teraswitch incident illustrates a different failure mode: finality risk without a production halt. The network's design absorbed the event within its tolerance, but the margin was 4.5 percentage points.