Public RPC eth_getLogs Limits

eth_getLogs error messages from public RPCs, explained

Exact error strings returned by free RPC endpoints when an eth_getLogs range is too large, what each means, and the fix. Collected on 2026-11-13.

limit exceeded

BNB Chain dataseed nodes refuse eth_getLogs for any range. Use a different BSC endpoint.

Seen on: bsc-dataseed1.bnbchain.org, bsc-dataseed2.bnbchain.org, bsc-dataseed3.bnbchain.org, bsc-dataseed4.bnbchain.org, bsc-dataseed1.defibit.io, bsc-dataseed2.defibit.io, bsc-dataseed3.defibit.io, bsc-dataseed4.defibit.io, bsc-dataseed1.ninicoin.io, bsc-dataseed2.ninicoin.io, bsc-dataseed3.ninicoin.io, bsc-dataseed4.ninicoin.io

public endpoint only serves recent blocks (last 1024). Register at blockreq.com for historical / archive access.

BlockReq public endpoints only serve roughly the last 1,024 blocks. Fine for live tailing, not for history.

Seen on: base-rpc.blockreq.com/v1/rpc/public, arbitrum-one-rpc.blockreq.com/v1/rpc/public, optimism-rpc.blockreq.com/v1/rpc/public, polygon-bor-rpc.blockreq.com/v1/rpc/public, avalanche-rpc.blockreq.com/v1/rpc/public

ranges over 10000 blocks are not supported on free plan

dRPC free tier: ranges over 10,000 blocks are rejected, and larger ranges often time out well before that. Use chunks of 100 to 1,000 blocks.

Seen on: eth.drpc.org, arbitrum.drpc.org, optimism.drpc.org, polygon.drpc.org, avalanche.drpc.org

eth_getLogs is limited to 0 - 50 blocks range

1RPC allows only 50 blocks per eth_getLogs call. Use another endpoint for history scans.

Seen on: 1rpc.io/arb, 1rpc.io/op, 1rpc.io/matic, 1rpc.io/sepolia

exceed maximum block range: 50000

PublicNode caps the range at 50000 blocks. Split the query into chunks of at most 50000 blocks.

Seen on: base-rpc.publicnode.com, avalanche-c-chain-rpc.publicnode.com, base-sepolia-rpc.publicnode.com

method is not available on the public endpoint

eth_getLogs is disabled on this public endpoint.

Seen on: api.blockvectra.com/v1/base_mainnet/public, api.blockvectra.com/v1/arb_mainnet/public, api.blockvectra.com/v1/eth_sepolia/public

Archive requests require a personal token. Get one at: https://www.allnodes.com/publicnode

PublicNode treats older blocks as archive data and needs a free token. Stay within recent blocks or get a token.

Seen on: ethereum-rpc.publicnode.com, arbitrum-one-rpc.publicnode.com, optimism-rpc.publicnode.com

service temporarily unavailable

Transient outage; retry with backoff.

Seen on: rpc.mevblocker.io, rpc.mevblocker.io/noreverts, rpc.mevblocker.io/fullprivacy

block range greater than 2000 max

The provider rejected the range. Halve the range and retry.

Seen on: rpc.flashbots.net, rpc.flashbots.net/fast

eth_getLogs is limited to a 10,000 range

The node allows at most 10,000 blocks per call. Chunk by that size.

Seen on: mainnet.optimism.io, rpc-mainnet.matic.quiknode.pro

request limit reached

Rate or request limit hit. mainnet.base.org refused even small getLogs calls during our test; use a different Base endpoint for log scans.

Seen on: mainnet.base.org

invalid params

Tenderly gateway rejected the larger range (it worked up to 1,000 blocks on Base).

Seen on: base.gateway.tenderly.co

block range exceeds limit of 1000 blocks

The provider rejected the range. Halve the range and retry.

Seen on: rpc.baseazul.dev

query exceeds max block range 2000

The provider rejected the range. Halve the range and retry.

Seen on: base.daybreak-rpc.network

exceed maximum block range: 10000

PublicNode caps the range at 10000 blocks. Split the query into chunks of at most 10000 blocks.

Seen on: polygon-bor-rpc.publicnode.com

block range too large: total block range in this request exceeds the maximum of 100 blocks

Avalanche public API rejects ranges above its configured maximum (we saw failures above 100 blocks). Chunk small.

Seen on: api.avax.network/ext/bc/C/rpc

Rate limit exceeded on Nodies public endpoints. For higher limits, create a free account at https://nodies.app and use a private endpoint. Enterprise: sales@nod

BNB Chain dataseed nodes refuse eth_getLogs for any range. Use a different BSC endpoint.

Seen on: 1rpc.io/avax/c

eth_getLogs is limited to a 200 range

The node allows at most 200 blocks per call. Chunk by that size.

Seen on: sepolia.base.org

eth_getLogs range of 1000 blocks exceeds the 500-block limit for this plan; split the request into ranges of at most 500 blocks

The provider rejected the range. Halve the range and retry.

Seen on: base-sepolia-rpc.blockreq.com/v1/rpc/public

Request timeout on the free plan, please upgrade to paid plan

dRPC free tier timed out. Reduce the range.

Seen on: base-sepolia.drpc.org

getLogs request exceeded max allowed range

The node has a fixed maximum range; chunk smaller.

Seen on: rpc.sepolia.ethpandaops.io

pruned history unavailable

The node pruned older history; query recent blocks only.

Seen on: ethereum-sepolia-rpc.publicnode.com

block not available: block not found for eth_getLogs, requested toBlock 12126777 is not yet available on the node (latestBlock: 12126776, finalizedBlock: 121267

The provider rejected the range. Halve the range and retry.

Seen on: ethereum-sepolia-rpc.blockreq.com/v1/rpc/public

Generic fix

// Chunked eth_getLogs that adapts to the provider's limit (viem)
async function getLogsChunked(client, filter, from, to, step = 2000n) {
  const out = [];
  for (let start = from; start <= to; ) {
    const end = start + step - 1n > to ? to : start + step - 1n;
    try {
      out.push(...await client.getLogs({ ...filter, fromBlock: start, toBlock: end }));
      start = end + 1n;
    } catch (e) {
      if (step === 1n) throw e;
      step = step / 2n; // range or result-size limit: halve and retry
    }
  }
  return out;
}