JSON-RPC error messages, explained
35 exact error strings, grouped by what went wrong. Every one was returned by a real node when we triggered that error class on 2026-09-24 across the EVM chains we serve, and each page lists the chains that returned it. Paste your error into the page search to find it.
- exceed maximum block range: 50000 (and every other eth_getLogs range error)eth_getLogs
exceed maximum block range: 50000exceed maximum block range: 10000Block range is too large
- Please specify an address in your request (eth_getLogs without an address)eth_getLogs
Please specify an address in your request or, to remove restrictions, order a dedicated full node here: …query exceeds max results 20000, retry with the range …-…query returns too many logs, narrow your filter: 20000
- the method debug_traceTransaction does not exist/is not available (-32601)debug_*, trace_*
the method debug_traceTransaction does not exist/is not availablethe method trace_block does not exist/is not availableMethod not found
- typed transaction too short / failed to decode signed transactioneth_sendRawTransaction
typed transaction too shortfailed to decode signed transactiontyped transaction too short
- missing trie node (state at a past block is pruned)eth_getBalance, eth_call, eth_getStorageAt at a past block
missing trie node <hash> (path ) state …state at block #2 is prunedheight 1 is not available, lowest height is …
- header not foundeth_call, eth_getBalance, eth_getBlockByNumber
header not found
- debug_traceTransaction: transaction not found / genesis is not traceabledebug_traceTransaction
transaction not foundtransaction not foundgenesis is not traceable
- method is not available on free plan / Unsupported subscription: newHeads (eth_subscribe)eth_subscribe (WebSocket)
method is not available on free plan, please upgrade to paid planUnsupported subscription: newHeadsthe method eth_subscribe does not exist/is not available
See also: JSON-RPC error codes decoded, method support by chain.