Solana Staking Outage: 28.83% of Staked SOL Briefly Goes Offline After Routing Failure

Solana’s staking ecosystem faced a significant disruption on [Date] when a routing failure at Teraswitch, a staking infrastructure provider, temporarily pushed 28.83% of all staked SOL offline. The incident, which lasted approximately 33 minutes, affected around 90 validators and brought the network dangerously close to the 33.34% threshold that could have halted transaction confirmation.

What Happened During the Outage

Marinade Finance, a leading liquid staking protocol on Solana, reported that the outage was triggered by a routing failure at Teraswitch. According to their analysis, AS20326, the autonomous system number associated with the provider, held 118.9 million SOL, representing 27.34% of the network’s total staked SOL. Of that amount, 94% went offline simultaneously, causing a sharp drop in network participation.

The affected validators missed a combined 333 SOL in staking rewards during the brief period. Traffic normalized after about 33 minutes, but the event has raised serious questions about the resilience and concentration risks inherent in Solana’s staking infrastructure.

Why This Matters for Solana’s Decentralization

The incident underscores a critical vulnerability in Solana’s validator ecosystem: the concentration of stake within a single autonomous system or data center. When a large portion of staked SOL is controlled by entities sharing the same infrastructure, a single point of failure can have outsized effects on network stability.

Marinade Finance highlighted that the outage was not caused by a flaw in Solana’s core protocol but rather by the failover infrastructure and routing systems used by Teraswitch. This distinction is important, as it points to operational risks rather than consensus-level issues.

However, the proximity to the 33.34% threshold—the point at which the network cannot finalize transactions—is a stark reminder of how close Solana came to a more severe disruption. Had the outage lasted longer or affected a slightly larger share of stake, the network could have faced a halt, impacting applications, users, and market confidence.

Concentration Risks and Industry Implications

This event is not isolated. It reflects broader concerns about staking centralization across proof-of-stake networks. Validators often rely on cloud providers like Amazon Web Services or specialized data centers, creating shared points of failure. The Solana network has previously experienced outages due to resource exhaustion and other issues, but this incident highlights a different kind of risk—one tied to the infrastructure layer.

For stakers and delegators, the event serves as a reminder to diversify across validators and infrastructure providers. For protocols like Marinade, it raises questions about how to set concentration caps to mitigate such risks. Marinade has stated it plans to review its concentration cap standards, which could lead to stricter limits on stake distribution across ASNs and data centers.

Conclusion

The temporary offline event involving 28.83% of staked SOL is a significant operational incident that exposes the fragility of staking infrastructure on Solana. While the network recovered quickly, the close call with the transaction halting threshold is a wake-up call for the ecosystem. Addressing concentration risks will be essential to ensuring long-term network resilience and maintaining trust among users and institutional participants.

FAQs

Q1: What exactly caused the Solana staking outage?
The outage was caused by a routing failure at Teraswitch, a staking infrastructure provider. This failure affected the connectivity of validators operating under the AS20326 autonomous system, taking 94% of the stake held by that system offline.

Q2: How close did Solana come to halting transaction confirmation?
The outage pushed 28.83% of staked SOL offline, which is close to the 33.34% threshold. If more than one-third of the stake is offline, the network cannot reach consensus to finalize transactions, effectively halting the chain.

Q3: What are the broader implications of this incident?
The incident highlights concentration risks in staking infrastructure, where a single provider or data center can become a single point of failure. It may prompt protocols like Marinade Finance to tighten concentration caps and encourage stakers to diversify their validator selections to reduce systemic risk.