Slot has been skipped, or missing in long-term storage

The RPC node has already pruned the block data for this slot. Standard nodes keep approximately 2 epochs (~2 days) of block history.

Common causes

1. Requesting old data from a non-archive node. Most RPC providers offer standard nodes that retain only recent data. Historical queries need an archive node.
2. Slot was skipped and pruned. The slot was already skipped (no block produced), and has since aged out of the node’s retention window.

How to fix

1. Use an archive RPC node. Archive nodes retain the full ledger history from genesis. Switch your RPC endpoint to an archive-tier provider.
2. Check if the slot exists. Use getBlocks on a recent range to verify the slot was not skipped before assuming the data was pruned.
3. Use Bigtable-backed nodes. Validators with Google Bigtable integration retain full history, but access is typically limited to archive-tier plans.

Retention periods

FAQ

How do I check if my RPC provider is archive? Try fetching a known old slot with getBlock. If it returns data, the node has archive capability. If -32009, it does not.

Is this the same as -32007? No. Error -32007 confirms a slot was skipped. Error -32009 means the data was once available but has been pruned from this node.

How much storage does a full archive node need? As of 2026, a full Solana archive (Bigtable) requires several petabytes of storage.

Updated: 2026-10-21