Solana outage 2026 scare on 12 August was not a blockchain shutdown, but a routing issue at Solana’s infrastructure as a service provider, TeraSwitch, which temporarily disconnected validators with 28.83% of all staked SOL▲$82.41, putting the network within 4.51 percentage points of the stake percentage at which transactions would be halted.
Contents
- Solana Outage 2026: What Happened to the Network?
- How Close Did Solana Come to a Network Halt?
- What Caused the Solana Validator Failure?
- Is Solana Centralized? What the Outage Revealed
- What Does the Solana Outage Mean for SOL Price?
- Solana Outage vs. Previous Network Problems
- Can Solana Prevent Another Validator Outage?
- What Does the Solana Outage Mean for SOL’s Next Rally?
- Solana Outage 2026: Should SOL Investors Be Worried?
- FAQ
Solana Outage 2026: What Happened to the Network?
Solana continued processing and finalizing transactions despite the validator being down, showing that the issue was one of infrastructure concentration rather than a failure of Solana consensus system.
Why Nearly 29% of Staked SOL Went Offline
Solana validator outage issue resulted in around 90 validators going offline, and 28.83% of Solana network stake becoming delinquent for around 33 minutes — 28.83% of the stake behind the validators was affected.
The scale of the event also illustrated TeraSwitch’s position as one of the largest stakeholders in Solana infrastructure. TeraSwitch was the largest holder of the data-center network, with approximately 30.8% of the stake prior to the event.
Read More: What Is USOH Crypto? The New Solana Energy Token Sparking RWA Investment Buzz
The Teraswitch Routing Failure Explained
Teraswitch routing failure was due to underlying issues with the network infrastructure, not Solana protocol code. As indicated on TeraSwitch’s status page, the issues were caused by a routine configuration change which was subsequently removed, and further protections and software upgrades were applied.
Other reports on the incident suggest that a default route originating from Miami propagated through a route reflector in Amsterdam. This is why the incident was able to take multiple validators offline in parallel in multiple other locations.
| Solana August 2026 Incident | Key Detail |
| Date | August 12, 2026 |
| Primary cause | TeraSwitch routing infrastructure failure |
| Affected stake | 28.83% of staked SOL |
| Validators affected | Around 90 |
| Delinquent-stake period | Around 33 minutes |
| Critical finality threshold | 33.34% delinquent stake |
| Distance from threshold | About 4.51 percentage points |
| Did Solana stop? | No — transactions continued to be processed and finalized |
How Long Did the Solana Outage Last?
Solana outage August 2026 had a 33 minute delinquent stake period according to the incident report and Solana Compass, but TeraSwitch fixed the routing problem much earlier, with reports showing a technical duration of 10 minutes at the longest.
This is a relevant distinction; however, validators can be delinquent while connectivity and voting are recovering from fixing the original problem, so the 33 minutes was not a complete blockchain downtime, but just a temporary validator-connectivity issue.
Did Solana Actually Stop Processing Transactions?
No. Despite headlines around a Solana network outage, the mainnet continued processing transactions throughout the incident. The affected stake peaked at 28.83%, below the 33.34% threshold associated with losing finality.
Unlike a subsequent outage on Solana in February 2024, in which block production was halted for about five hours, the network was able to reach consensus and finalize transactions in August, although the validators were at the edge of fault tolerance.
How Close Did Solana Come to a Network Halt?
At the peak of the event on August 12, 28.83% of the staked SOL was considered suboptimal or delinquent, a record high. This value was 4.5 percentage points away from the finality threshold of 33.34%, meaning that according to Solana Compass, the network was within 4.5 points of a finality halt.
Although not a complete Solana network failure (as blocks were still being produced and transactions were landing), there was risk that the remaining online stake would not have the supermajority required for finality.
Why 33.34% Is the Critical Threshold
Solana’s Tower BFT is stake-weighted, so for a block to reach finality, more than two-thirds (66.67%) of SOL staked to validators must vote for the same chain. If more than a third of the voting stake enters a delinquent state, the supermajority will no longer be obtainable for agreeing on new blocks.
Note that crossing the threshold does not stop other validators from producing blocks before finality has been achieved; a new block can be produced even if it does not reach a sufficient voting stake to mark itself as final.
What 28.83% of Staked SOL Going Offline Means
Note that Solana 28.83% staked SOL number refers to the stake delegated to validators that became delinquent, and not to the stake delegated to all validator machines. Reports based on the Marinade Finance analysis put the number of affected validators at around 90.
After accounting for their effective stake of 28.83% (roughly 86% of the 33.34% finality threshold), SolanaFloor had around 20 million SOL of stake remaining as a buffer.
The episode demonstrated the importance of stake distribution, and how a small number of validators could represent a disproportionate amount of consensus weight on the network when also combined with a disproportionately high amount of delegated SOL stake among those validators.
Read More: The Altcoin Season Index Is Still Below 50: What Needs to Happen Before Altseason Begins?
Why Solana Kept Finalizing Transactions
Since at all times more than two-thirds of stake continued to be able to vote, and the delinquent share of stake never reached the 33.34% supermajority threshold needed for Tower BFT, Solana continued to finalize.
This is why reports describing 28.83% Solana validators offline need careful interpretation: 28.83% represented stake, while approximately 90 validators were affected. Solana’s documentation describing its consensus explicitly states it is stake weighted, not equal weight per validator.
How Validator Concentration Increased the Risk
This was further exacerbated by the concentration of infrastructure, as SolanaFloor reported that the affected TeraSwitch autonomous system, AS20326, hosted approximately 27.34% of Solana’s staked SOL, meaning that the failure to connect to a single individual infrastructure provider could also translate into issues with a substantial amount of the consensus stake.
This is, of course, the kind of correlated failure that infrastructure diversification seeks to avoid. For example, Coinbase reports in its Solana validator report for Q1 2026 that it actively splits its Solana validators between TeraSwitch and Latitude to reduce the “blast radius” of a provider outage.
As a result, the August event highlighted a concentration issue with Solana validators, rather than a failure in Solana’s consensus mechanism: a set of stake-heavy Solana validators were running on infrastructure that thus could fail together.
What Caused the Solana Validator Failure?
The August 12 Solana validator failure was a failure outside Solana’s consensus implementation where TeraSwitch, a major validator infrastructure provider, made a routing failure that affected a large proportion of Solana stake. At its peak, Marinade Finance reported that 28.83% of staked SOL was delinquent as a result.
The voting power of the network has been preserved and so the incident reflects a failure in the infrastructure and connectivity rather than the consensus of Solana.
How a Routing Error at TeraSwitch Affected Validators
TeraSwitch Solana outage was a result of a routing problem in the provider’s network that caused the affected validator servers to be unable to remain connected for standard operation.
Marinade claims to have discovered 90 validators that were affected, and although other statistics show that at one point 597 of 699 validators voted, this does not prove that all non-voting validators were affected by TeraSwitch fault.
Why Multiple Data Centers Lost Connectivity
In fact, TeraSwitch noted that the routing event affected 12 different sites, helping to explain why validators at different data centers could potentially lose connectivity at roughly the same time.
Reports suggest that Solana routing failure originated at TeraSwitch’s facility in Miami, but affected connectivity at many other places.
The Role of Validator Infrastructure Concentration
The disruption was proportional to the concentration of infrastructure: for example, Marinade, which used TeraSwitch (AS20326), held 118.89 million SOL or 27.34% of staked SOL, and on that AS, just below 94% of stake went offline.
In the 2025 Solana Foundation network health report, TeraSwitch again emerged as the largest hoster by stake, and the geographic concentration around major low-latency data centers was 24.28%.
Solana routing outage shows that more infrastructure providers do not necessarily lower the risk of correlated failure if a large share of stake depends on one provider.
Could the Same Problem Happen Again?
A future outage affecting a large number of Solana’s validators has not been ruled out. Solana Foundation considers infrastructure distribution a resilience issue; no single data center or country should have more than a third of the network’s stake.
The August incident showed that a provider-level routing issue can impact validators with almost 29% of stake at once. Reducing correlated exposure is critical, as is having a diverse infrastructure setup.
| Validator Infrastructure Risk | August 2026 Incident |
| Infrastructure provider | TeraSwitch |
| Affected autonomous system | AS20326 |
| Sites affected | 12 |
| Validators affected | Around 90 |
| Stake on AS20326 | 118.89 million SOL |
| Share of network stake on AS20326 | 27.34% |
| Stake on AS20326 that went offline | Nearly 94% |
| Main risk exposed | Correlated infrastructure failure |
Is Solana Centralized? What the Outage Revealed
The August episode, while not proving Solana is centralized, shows the risk of concentration in a system, as a TeraSwitch routing failure caused 28.83% of staked SOL to be in a delinquent state. Quorum stake in consensus can rely on shared infrastructure.
Solana Foundation’s June 2025 report stated that validators are hosted through more than 100 data-center providers in 40 countries, but TeraSwitch hosted 24.28% of the stake.
How Many Validators Were Affected?
Marinade Finance estimated that 90 Solana validators were affected and that 28.83% of staked SOL became delinquent for around 33 minutes.
That answers how many Solana validators went offline only approximately: this is around 90 validators, or 28.83% of the stake, which is not equivalent to what share of the validator population.
Why Infrastructure Providers Matter for Solana
Because the validator nodes rely on network and server infrastructure, Solana Foundation considers it a systemic risk when there is a high stake concentration in an ASN or hosting company that goes offline.
Marinade’s risk materialized, with TeraSwitch acknowledging a routing issue in 12 locations in August. Marinade reported that 27.34% of network stake was delegated to its AS20326, and 94% of the stake went offline during the incident.
Validator Diversity vs. Stake Concentration
Other metrics have been proposed because the number of validators is not a good measure of Solana’s decentralization: Solana’s consensus is determined by stake-weighting, and hundreds of independent Solana nodes can provide large voting powers by being on the same server or network.
The Foundation opted for delegation rules: from May 2026, validators must each belong to an ASN and a hosting provider with at most 25% of the stake, and total data center concentration must remain less than 15%.
The August disruption proved the case for these limits, as TeraSwitch’s compromised autonomous system held over 25% of all staked SOL.
Read More: Crypto Market Industry Shakeout 2026: Why Crypto Is Entering a Major Consolidation
What Solana Needs to Improve After the Outage
The core difficulty is reducing correlated infrastructure risk, which is likely best addressed by further dispersing hosting providers, ASes, and physical locations, since this can further limit the amount of stake a single provider failure may disconnect, in line with the existing concentration limits of the Foundation.
Infrastructure diversity is already a formal Solana Foundation Delegation Program goal, which seeks to maximize decentralization and reliability, and lists 59 delegations in 24 countries.
It argued Solana’s future would depend both on having a large number of validators and avoiding overly centralizing shared infrastructure.
What Does the Solana Outage Mean for SOL Price?
For those asking what happened to Solana today, the August incident exposed a serious infrastructure risk, but the network never completely stopped; 29% of staked SOL was left delinquent after TeraSwitch routing failed, while Solana continued processing and finalizing transactions as normal.
This distinction is relevant to price risk because previous outages have caused large price swings to SOL, although the network has continued operation despite the infrastructure outage.
Why Network Reliability Matters for SOL Investors
Reliability as the foundation for financial trading, payments, and decentralized applications may impact confidence in Solana. Disclosures concerning SOL investments note that its value may be adversely affected since blockchain outages can disrupt the process of transferring SOL, or create uncertainty concerning the reliability of the network.
For investors asking what caused Solana outage, the immediate issue was external routing infrastructure rather than a consensus bug. That reduces one category of concern, but the concentration exposed by the incident remains relevant to Solana’s risk profile.
Could the Outage Trigger Short-Term Selling?
This negative headline could create a knee-jerk selling reaction, but it is not realistic to say that this was the sole factor for the sell-off. On the daily chart at the time, SOL was back to around the $76.14 level on 13 August, which is the range of the post-June sell-off.
For investors asking is Solana down today, the answer is no: the network continued processing and finalizing transactions during the incident.
Another connectivity issue, or the loss of finality, would be a materially more serious catalyst than the August 12 incident, when transactions continued being processed.
Why SOL Could Recover Despite the Validator Failure
The best argument against the bear thesis from outages is that Solana withstood the first-level stress test. 28.83% of Solana’s stake went delinquent, but there was enough stake remaining to support finality, and the network did not need to restart.
More recent network usage data is somewhat of a counterbalance. Usage statistics shared by validator operator Everstake show Solana processed 171.9 million non-vote transactions on August 10, suggesting the network was already busy leading up to the event.
SOL Price Levels to Watch After the Outage
On the daily chart as of August 13, SOL was at $76.14. The short-term technical support was at the $72-$74 area, while the more important support level was at the June-July lows around $62-$65. On the positive side, the first meaningful resistance area is around the $80-85 levels. A convincing breakout from there would support bullish short-term structure.
Momentum is neutral to positive. The daily RSI is 54.40, compared with a seven-day average of 48.54. The histogram of the MACD has moved into positive territory.
SOL therefore does have some improving momentum, but confirmation above the $80-85 range would provide a more convincing case from a technical indicators standpoint.
| SOL Price Indicator | Level / Reading | What It Signals |
| SOL price | $76.14 | Current reference level |
| Immediate support | $72-$74 | First key downside zone |
| Major support | $62-$65 | June-July support area |
| Resistance | $80-$85 | Key breakout zone |
| Daily RSI | 54.40 | Neutral-to-positive momentum |
| MACD histogram | Slightly positive | Improving short-term momentum |
Solana Outage vs. Previous Network Problems
Unlike past full Solana outages, the network did not fully stop during this outage. A routing issue on TeraSwitch caused a large portion of Solana’s stake to go offline, but enough stayed online to continue finalizing.
In contrast, the February 6, 2024 incident caused block finalization to stop for around five hours, requiring a validator restart.
This meant that the failure modes were different, as the 2026 failure was caused by connectivity issues, while the 2024 failure was caused by validator software.
How the 2026 Incident Differs From Earlier Solana Outages
The February 2024 Solana network outage was caused by a bug in the LoadedPrograms cache, which Solana said caused an infinite loop, stopped consensus progress, and required validators to restart the cluster with patched software.
It did not happen in 2026, and Finality survived, meaning there was no network-wide restart or multi-hour consensus interruption.
Why This Was a Connectivity Failure Rather Than a Consensus Failure
In 2024, a software bug directly stopped consensus. In August 2026, validators affected by a routing infrastructure problem lost connectivity. Validators that remained online, however, continued voting and finalizing blocks.
That makes what caused Solana validator failure materially different from 2024: not an issue in the consensus code but rather reliance on shared network infrastructure.
Has Solana Become More Resilient Since 2024?
On Solana’s resiliency, as reported by Solana Foundation in June 2025, uptime on the network was 100% for almost 16 months, including through record-high levels of activity in January 2025.
Client diversity has also increased, as the Foundation noted Agave running with the new Firedancer implementation, and Solana’s changelog for July 2026 listed active releases for both clients.
However, the events of August 2026 show that better software resilience does not eliminate infrastructure risk. Solana network will continue to face this risk at protocol and client levels if an important percentage of its validators are hosted on the same infrastructure.
Can Solana Prevent Another Validator Outage?
While Solana cannot prevent infrastructure failures, the August incident highlights one potential area of focus: correlated validator exposure. Currently, Solana Foundation only delegates to validators hosted by providers or ASNs that hold 25% or less of the stake in the entire Solana network, and 15% or less within individual data centers.
Note that while those rules speak to the type of concentration seen during Solana routing outage, they only apply to who the Foundation can delegate to and not all validators.
Redundancy and Failover for Solana Validators
Solana validators should keep redundancy in the hosting and internet transit layers. The Foundation has warned that such a concentration of stake in a single ASN or hosting company exposes the network to systemic risk during outages.
Partially, it makes a case for infrastructure redundancy, in diversity of connectivity, hosting locations, and hosting providers to not be affected at once in the same failure domain.
Read More: Congress Crypto Bill Delay: CLARITY Act Vote Pushed to September as 2026 Passage Hopes Fade
Reducing Dependence on Individual Infrastructure Providers
Solana’s current delegation requirements are a mechanism for distribution. As of 1 May 2026, Foundation-backed validators must run with an ASN and hosting provider that hold less than 25% of network stake. Data center operators must hold less than 15% of network stake.
These limits will not prevent another Solana network outage scare; however, they should discourage concentrations that cause an issue on infrastructure providers to pose a risk to the liveness of the network.
How Alpenglow Could Improve Solana’s Reliability
Alpenglow is a proposed replacement for TowerBFT on Solana, using the Votor voting protocol, where consensus is achievable with 20% of stake being adversarial, another 20% being offline, and finality is reached with about 150 ms of latency.
Alpenglow cannot be seen as a final solution for Solana routing failure. Anza says developers are testing the network with faults, and Solana says issues with the community test cluster are still being resolved before migration. Agave 4.2 included Alpenglow code for testing, but it was to be enabled in Agave 4.3.
What the Solana Developer Community Needs to Fix
More broadly, it is more than just consensus code: concentrated infrastructure is systemic risk, and to address it we need to reduce correlated dependence on individual ASNs, hosting companies, and data centers.
Anza states that it has hardened Agave and increased the adversarial testing for the software, and the current Alpenglow development includes network-fault and equivocation stress tests.
So the goal is not a single patch for why is Solana having an outage but building more resilient systems across the independent layers of the validator infrastructure, client software, and consensus protocol.
What Does the Solana Outage Mean for SOL’s Next Rally?
Solana outage today adds a new risk factor to SOL’s recovery narrative, but the incident did not halt finality. On August 12, 28.83% of staked SOL became delinquent after TeraSwitch’s routing failure, yet the network continued operating.
For SOL, such a rally would likely depend on demand and confidence that the underlying infrastructure weaknesses exposed by the Pyth incident can be contained and adequately managed.
The Bullish Case for SOL After the Outage
A bullish counter is that Solana stayed online despite hovering near the one-third delinquent-stake threshold. SOL’s official status data shows 100% Mainnet Beta uptime across May, June, and July 2026 before the August routing incident.
Access to Solana through ETFs also increased; Block estimated that Solana ETFs had $904 million of total assets under management in July. Additionally, Morgan Stanley’s spot Solana product began trading on NYSE Arca on July 28. Such products provide new demand channels besides the native crypto markets.
The Bearish Case: Why Validator Risks Could Weigh on SOL
A bearish case involves how close the network is to losing finality. The outage forced 28.83% of the stake to become delinquent, affecting about 90 validators, which indicates correlated exposure to the underlying infrastructure.
If a repeat caused the amount of delinquent stake to exceed the consensus threshold, confidence could be further damaged. Therefore, infrastructure centralization is a material risk that is worth monitoring, even if it was not a consensus failure.
Key SOL Price Levels and Catalysts to Watch
With SOL price chart trading around $76.14, an important resistance level is observed around the $80-85 range, whereas a key support range is noted at around $72-74, followed by the June support around the $62-65 range.
ETF demand and network upgrades could be potential catalysts. Solana suggests using Agave 4.2 on mainnet, which will become effective in August; features of Agave 4.2 are projected to be available the week of 17 August. Alpenglow is under testing and expected to be released as Agave 4.3.
What Would Confirm the Next Solana Rally?
Technically, consolidation above the $80-85 resistance area will support the daily chart setup. However, considering the RSI reading of 54.40 and the slightly positive MACD histogram, such a breakout may not be confirmed by the indicators at this stage.
Confirmation would be stronger if the network was more stable and if there was a path to sustainability in institutional interest. Since there have been multiple SOL investment products launched and periodic upgrades, price momentum and stability would matter more than an ephemeral price surge after Solana validator failure.
| SOL Rally Factor | Bullish Signal | Bearish Risk |
| Network reliability | Finality remained intact | 28.83% of stake became delinquent |
| Institutional demand | Growing ETF access and AUM | Demand may weaken with sentiment |
| Technical setup | Break above $80-$85 | Loss of $72-$74 support |
| Network upgrades | Agave 4.2 and Alpenglow progress | Upgrade benefits are not guaranteed |
| Rally confirmation | Sustained move above resistance | Renewed validator disruption |
Solana Outage 2026: Should SOL Investors Be Worried?
Solana outage 2026, a warning but not a network shutdown, occurred on 12 August when 28.83% of staked SOL became delinquent due to a failure to route transactions through TeraSwitch. 90 validators were affected for 33 minutes. Solana nevertheless stayed below the 33.34% threshold at which finality would have been lost.
For investors, this highlights the risk of infrastructure concentration: consensus worked, but this episode shows that an issue with a single infrastructure provider can still affect a large amount of voting stake at once.
The Biggest Risks After the Validator Failure
One of the key lessons from Solana validator failure is correlated infrastructure dependence. Marinade later discovered that TeraSwitch AS20326 has 27.34% of the network stake, of which 94% was taken offline.
Solana’s criteria for what validators may delegate also acknowledge the problem: a concentration of stake within an ASN or hosting provider is a systemic risk. Since May 2026, the Foundation-approved validators must operate on an ASN or hosting provider which, in total, does not operate more than 25% of the total amount of stake in the network. The limit is 15% for data centers.
The Strongest Arguments for a SOL Recovery
The positive is that the network absorbed the blow and finality was not lost. Beyond that, SOL has other drivers of demand. Solana reported over $1B of spot ETF AUM in May and all-time highs of real-world assets and tokenized stocks.
More recently, according to Solana Compass, there were net inflows into U.S. spot Solana ETFs on every trading day of the first week of July.
That does not mean a price recovery is guaranteed, but the investment case is no longer entirely about Solana network failing as it was in August.
Read More: Best Crypto Tokens Under $5 to Buy Before the Next Big Rally
Solana’s Next Test: Reliability, Decentralization and Growth
Solana now has three concrete metrics to track: finality under load, infrastructure concentration, and ecosystem demand. The foundation’s existing delegation rules around ASN, hosting provider, and data center concentration already provide a path towards improving infrastructure decentralization.
In addition to reliability, growth must follow. In May, Solana announced that it became the biggest RWA ecosystem with over $2.8 billion and $1 billion in spot ETF AUM. This gives investors a concrete measure to follow rather than just making speculative price plays.
That means the event in August is neither irrelevant nor proof that the network is broken. The next step for SOL investors is whether Solana can build on those gains while reducing the correlated infrastructure risk that almost cost it finality.
FAQ
What happened during the August 2026 Solana incident?
For those asking why did Solana go down, a routing issue at TeraSwitch caused validators representing 28.83% of staked SOL to lose connectivity, but the network continued to finalize transactions.
Did Solana completely go down in August 2026?
No. Solana continued to process and finalize transactions throughout the incident because the voting stake remained online (unlike the full network halt in February 2024).
How close was Solana to losing finality?
It reached a peak of 28.83% delinquent stake, which meant that 33.34%, or more, of validators going offline could force the network to be unable to achieve a two-thirds supermajority in order to finalize blocks.
Could another validator connectivity incident happen?
Yes. While provider, routing, and data-center failures cannot be eliminated, having a more distributed and redundant infrastructure can avoid impacting a large share of stake at once.
Could the incident affect SOL’s price?
Network reliability is relevant to investor sentiment; SOL price would still be affected by other factors, including market conditions, institutional demand, network activity, and future technical developments.
