Receiving an Unsupported Block Number error

Hello! Our logs are reporting an occasional error from Arbitrum related to an “Unsupported Block Number …”. The code is calling an ERC20 balanceOf function with the latest block. I’ve attached an error trace that appeared at 11-08-2022 10:11:59.568 (the block appeared at 11-08-2022 10:11:42).

Because we’re using the latest blockTag, I’m curious as to why this error is appearing. The docs have been sparse.

Thanks in advance!

{"reason":"processing response error","code":"SERVER_ERROR","body":"{\"jsonrpc\":\"2.0\",\"id\":286,\"error\":{\"code\":-32000,\"message\":\"unsupported block number 19995050\"}}","error":{"code":-32000},"requestBody":"{\"method\":\"eth_call\",\"params\":[{\"to\":\"0x82af49447d8a07e3bd95bd0d56f35241523fbab1\",\"data\":\"0x70a08231000000000000000000000000xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"},\"latest\"],\"id\":286,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","url":"https://arbitrum-mainnet.infura.io/v3/{id}"}

Hi @james-a-morris how often you get this error ? I’ve tried to reproduce it without success.
Can you perhaps open a ticket and let us know the api key you were using so we could look into it.

Thanks !

We’re receiving about ~30 of these errors an hour (of the 540 that are transmitted). Adding a blockTag override of -1 brought down these errors by nearly half.

I can follow up with a support ticket. Thanks!

Hi folks,

We also get this error sporadically - if anything slightly more frequently than the approx 5% hit rate mentioned above;

(error={“reason”:“processing response error”,“code”:“SERVER_ERROR”,“body”:"{“jsonrpc”:“2.0”,“id”:48,“error”:{“code”:-32000,“message”:“unsupported block number 20456116”}}",“error”:{“code”:-32000},“requestBody”:"{“method”:“eth_call”,“params”:[{“from”:“0x647bfa8b0d0050dc00777d33ad20b3ce196ae50a”,“to”:“0x3b1b258ca111b9bae664b5a7ea8fb12ac0656551”,“data”:“0xd0c93a7c”},“latest”],“id”:48,“jsonrpc”:“2.0”}",“requestMethod”:“POST”,“url”:“https://arbitrum-mainnet.infura.io/v3/{id}”}, data=“0x”, code=CALL_EXCEPTION, version=providers/5.5.0)

thanks both, I’m looking into what might be causing this, it seems that the error comes from the node itself.