Why Has Solana Had Network Outages? Explained

Solana has experienced multiple full or partial network outages since 2021, most caused by resource exhaustion from transaction floods, software bugs in its consensus client, or bot-driven spam overwhelming validators before fixes like fee prioritization and QUIC networking were rolled out.

Unlike most established layer-1 blockchains such as Bitcoin or Ethereum, which have never had a chain-wide halt, Solana's history includes several episodes where block production stopped entirely and validator operators had to coordinate a manual restart. This is a meaningful reliability difference worth understanding if you use or hold assets on the network.

What actually happens during a Solana outage

Solana is designed for extremely high throughput, targeting thousands of transactions per second with sub-second block times. That performance comes from an architecture that pushes a lot of computation onto validator hardware and assumes network and memory resources stay within bounds.

When those assumptions break, the network doesn't just slow down, it can stop producing new blocks altogether. During an outage:

• New transactions are not confirmed and the ledger stops advancing.
• Validators typically detect the halt and coordinate off-chain, often over Discord or Telegram, to agree on a restart procedure.
• A restart usually requires a supermajority of stake-weighted validators to upgrade software and resume from an agreed-upon slot.

This manual coordination step is very different from how Bitcoin or Ethereum handle stress. Learn more about consensus mechanisms generally in our proof of stake glossary entry and see how different layer-1 blockchains compare in design philosophy.

The main causes behind past outages

Resource exhaustion from spam or bot traffic. Several outages, including a major one in September 2021, were triggered by bots flooding the network with transactions during high-demand events like NFT mints or token launches. Validators ran out of memory processing an unbounded queue of duplicate transactions.

Consensus or client bugs. A notable outage in 2022 stemmed from a bug introduced by a durable nonce feature that caused validators to fork onto different versions of the ledger, and the network couldn't reach consensus on the correct chain state.

Insufficient fee markets. For a long stretch, Solana lacked a robust local fee-market mechanism, so spam transactions cost about the same as legitimate ones. This meant an attacker or even an aggressive bot farm could clog the network cheaply.

What has changed since

Solana's core developers have shipped several upgrades aimed directly at these failure modes:

• QUIC transport protocol, replacing the older UDP-based gossip method, giving validators more control over which peers can send data and at what rate.
• Stake-weighted quality of service (QoS), prioritizing transactions from validators with higher stake, making spam floods less effective.
• Local fee markets, allowing transaction fees to rise for congested parts of the state (like a specific popular smart contract) without raising costs network-wide.
• Better client diversity efforts, since running a single dominant client software increases the risk that one bug takes down the entire network. Firedancer, an independent validator client built by Jump Crypto, is a direct response to this concern.

Should this affect how you use Solana?

If you hold funds in a Solana wallet or use Solana-based DeFi, an outage doesn't put your assets at direct risk of loss since your keys and balances remain intact once the network resumes. The risk is more about availability: you may be unable to trade, adjust a leveraged position, or exit a yield strategy during a halt, which matters most for time-sensitive positions.

It's also worth checking a chain's track record before committing significant capital, alongside metrics like TVL and decentralization of the validator set. Comparing outage history across ecosystems on our chains data pages can give useful context.

Solana outages compared to reliability efforts elsewhere

Factor	Solana (historical)	Typical mature L1 (e.g. Bitcoin, Ethereum)
Chain-wide halts	Multiple since 2021	None recorded
Recovery method	Manual validator coordination and restart	Not applicable, network self-heals
Root causes	Spam floods, client bugs, weak fee markets	N/A
Mitigations	QUIC, stake-weighted QoS, local fee markets, client diversity	Long-tested, conservative upgrade cadence
Throughput design	Optimized for very high TPS	Optimized for security and decentralization first

Bottom line

Solana's outages were driven by a combination of aggressive performance targets, immature fee markets, and reliance on a single dominant validator client, and the network has since made concrete engineering changes to reduce the odds of a repeat. That said, the manual restart process shows the chain's liveness guarantees are still less battle-tested than older, more conservative networks. If you're evaluating a chain for serious capital, checking its uptime history and client diversity is just as important as checking fees or TVL.