Solana network congestion
Congestion on Solana is competition for a scheduled leader slot, not a queue you wait in. What actually runs out, how the local fee market prices it, and why your transaction is dropped rather than delayed.
Open the reportSolana network conditions and what each state does to a trade
A cluster is not simply up or down. It moves through states, and each state has its own mechanism, its own signature on your screen and its own correct response. Congestion is competition for space inside a block. Degradation is a period where blocks are still produced but the experience of using the chain gets worse. Epoch turnover and client upgrades are scheduled or announced periods where behaviour is legitimately unusual for reasons that have nothing to do with you.
This section defines those states from public protocol and client documentation. It does not narrate specific events, does not assign dates to them, and does not publish figures for how often any of them occur. What it gives you instead is the vocabulary to say what is happening, which is the step everyone skips and the one that decides whether the next hour is spent usefully.
congestion competition Requests contend for a block; the loser is dropped, not queued
degradation gradient A band between healthy and halted, with several distinct symptoms
epoch turnover scheduled A boundary with predictable accounting and stake effects
upgrade window announced Client releases roll out unevenly across the validator set
3 reports in this section
The states the cluster can be in and what each one does to a trader: contention for block space, degraded periods where the chain runs but runs badly, and the scheduled windows around epochs and client upgrades.
What degraded looks like
Between healthy and halted there is a wide band where the chain produces blocks and still fails you. The symptoms of a degraded period, in the order a trader normally meets them.
Open the reportEpochs, upgrades and windows
Epoch boundaries, stake activation, validator client upgrades and feature gates create predictable periods of unusual behaviour. Which ones are scheduled, which are announced, and how to see them coming.
Open the reportHow the three states are told apart
The fastest way to name a state is to look at what is uneven. Congestion is uneven across accounts: one contended pool fails while the rest of the chain behaves. Degradation is uneven across time: the same request works, then does not, then does again. A scheduled window is uneven across validators: the outcome depends on which leader is producing when you send. Once you know which axis the unevenness sits on, the state names itself.
| State | What is uneven | Typical first symptom | Where you go next |
|---|---|---|---|
| Congestion | Across accounts and venues | One pair fails repeatedly while others land | Fee posture and transaction sizing |
| Degradation | Across time | Intermittent failures with no pattern by venue | Isolation tests, then official status |
| Epoch turnover | Across the boundary itself | Odd behaviour clustered around one moment | Your calendar and stake accounting |
| Upgrade window | Across validators | Outcome depends on which leader you hit | Client release notes and status notices |
Diagnosis Separating a chain-wide condition from an endpoint fault and from a mistake in your own request. The order of checks, the evidence each one produces, and where the official status signal actually lives. Open the section Response What to change while conditions are bad and what to do once they clear: sizing, fee posture, retry discipline, pausing rules, and the reading pass that turns an incident into a settings change. Open the section