What does a -32xxx code mean?

It is a JSON-RPC error code; each entry explains the specific cause and fix.

Why am I getting HTTP 429?

Rate limiting — back off and respect Retry-After, or raise your plan.

Which errors should I retry?

Retry 429 after Retry-After, and 503 with backoff. Do not retry 400, 401, 403 or 404, or a deterministic program error: the same request fails the same way.

Where are the methods documented?

In each network's docs; /docs/methods lists every method and the networks that support it.

Solana & EVM RPC error reference

Last updated: November 1, 2026

RPC errors
Error	Code	Category
Block cleaned up, does not exist on node	-32001	block
Block not available for slot	-32004	block
Transaction simulation failed: Blockhash not found	-32002	transaction
Forbidden	HTTP 403	transport
Too Many Requests	HTTP 429	transport
Internal error	-32603	jsonrpc
Invalid params	-32602	jsonrpc
Invalid request	-32600	jsonrpc
Account excluded from secondary indexes	-32010	account
Method not found	-32601	jsonrpc
Node is unhealthy	-32005	network
Parse error	-32700	jsonrpc
Transaction signature verification failure	-32003	transaction
Slot skipped, or missing in long-term storage	-32009	block
Slot skipped, or missing due to snapshot jump	-32007	block
execution reverted	3 / -32000	execution
nonce too low	-32000	transaction
already known	-32000	transaction
insufficient funds for gas * price + value	-32000	transaction
header not found	-32000	history
query returned more than N results	-32005 / -32000	logs
batch_too_large	HTTP 413	request
invalid conditional options: <field>: <reason>	-32602	transaction
robinhood_pendingBlock is not enabled	-32601	subscription
unauthorized	close 4001	authentication
scope_missing	close 4003	authentication
client_backpressure: reconnect and resubscribe	close 1013	subscription
feed resume window does not cover the cursor	bufferComplete=false	subscription
from_sequence must be an unsigned decimal integer	HTTP 400	request
beyond_retention	HTTP 410 / -32602	history
Transaction version is not supported	-32015	history
Transaction simulation failed	-32002	transaction
Computational budget exceeded	InstructionError	transaction
Insufficient funds for rent	InsufficientFundsForRent	transaction
custom program error: 0x…	InstructionError Custom	transaction
Minimum context slot has not been reached	-32016	read
Missing or unknown API key	HTTP 401	auth
Request body over the 64 KiB limit	HTTP 413	request
Upstream temporarily unavailable	HTTP 503	transport
Invalid JSON-RPC request	HTTP 400	request
endpoint_not_found	HTTP 404	request
WebSocket stream limit reached	WS close 4029	streaming
eth_getLogs capacity exhausted on BSC	HTTP 429 / -32005	logs

How to use this section

Check the HTTP status first: 4xx with a plain JSON body came from the gateway, 200 with an error object came from a node.
Find your error by message or code, including the -32xxx number or the Solana error name.
Follow the numbered fix, then the related methods to prevent it.

FAQ

What does a -32xxx code mean?: It is a JSON-RPC error code; each entry explains the specific cause and fix.
Why am I getting HTTP 429?: Rate limiting — back off and respect Retry-After, or raise your plan.
Which errors should I retry?: Retry 429 after Retry-After, and 503 with backoff. Do not retry 400, 401, 403 or 404, or a deterministic program error: the same request fails the same way.
Where are the methods documented?: In each network's docs; /docs/methods lists every method and the networks that support it.