Slot was skipped, or missing in long-term storage

The requested slot was skipped — no block was produced for it. This is normal behavior on Solana.

Why slots get skipped

A slot is skipped when the assigned leader validator fails to produce a block in time. Common reasons:

1. Leader offline or slow. The validator assigned to this slot was unreachable or could not build a block within the time window.
2. Network issues. Temporary connectivity problems prevented the leader from propagating the block.
3. High skip rates. During congestion or validator issues, skip rates increase.

The typical network-wide skip rate is 2–5%. Individual validators may have higher rates.

How to handle

1. Skip to the next slot. If you are iterating through slots, simply move to the next one. Not every slot produces a block.
2. Use getBlocks for ranges. Instead of checking slots one by one, use getBlocks to get a list of confirmed slots in a range.
3. Do not retry. A skipped slot will never have a block — retrying the same slot is pointless.

FAQ

Is a skipped slot an error? No. Skipped slots are a normal part of Solana’s operation. The network continues producing blocks in subsequent slots.

How many slots are typically skipped? On a healthy network, 2–5% of slots are skipped. During degraded conditions, this can increase significantly.

What is the difference between -32007 and -32004? Error -32007 confirms the slot was skipped (no block exists). Error -32004 means the block data is unavailable — the slot may have been skipped or the data pruned.

Updated: 2026-10-21