Transaction history is not available from this node

The RPC node does not have transaction history for the requested address or time range. This happens on nodes that do not store full transaction indexes.

Common causes

1. Node does not index transactions. Not all RPC nodes maintain a transaction history index. This feature requires additional storage and is often limited to paid tiers.
2. History was pruned. The node once had the data but has since pruned it due to storage limits.
3. The before or until signature points to a pruned range. When paginating with getSignaturesForAddress, the cursor may reference a transaction outside the node’s retention.

How to fix

1. Use a provider with transaction history. Switch to an RPC endpoint that maintains full transaction indexes.
2. Limit the query range. If you only need recent history, omit the before parameter or use a recent signature as the cursor.
3. Use an archive node. For complete historical data, use an archive-tier RPC provider with full transaction indexing.

FAQ

Why do some nodes not have transaction history? Maintaining a transaction history index requires significant disk I/O and storage. Many providers disable it on standard tiers to reduce costs.

How far back does transaction history go on a standard node? It varies by provider. Some keep no history, others retain a few hours to a few days. Check your provider’s documentation.

Can I get historical transactions another way? Yes. You can use getBlock to fetch all transactions in a specific slot, then filter by address. This works on any node that has the block data, though it is less efficient than the history index.

Updated: 2026-10-21