Project ID does not have access to archive state


We have been using Infura for a year (free tier) and we have been using calls that asked for the current balance in a specific block number (always the current block number but specified with its value, not with the string latest). A month ago we changed the request to ask for current block - 12, and we have been good until today. Today we started to receive this error project ID does not have access to archive state.

Searching in the docs we find:

“If you are interested in inspecting historical data (data outside of the most recent 128 blocks) for any of the methods listed below, your request requires access to archive data.”

We are interested in 12 blocks before the current, but when we ask for the balance in that block we get the error. We have tried also to ask for the current block (specified with the block number in hex, not with the string latest) and it also returns that error. It seems that the block_identifier argument behaviour has changed in Infura in some way. Could someone shed light on this matter?

I leave some raw requests tested:


curl [{]( PROJECT ID } \ -X POST \ -H "Content-Type: application/json" \ -d '{"jsonrpc": "2.0", "method": "eth_call", "params": [{"to": "0x8937830378298F7cdd479d27c410e7853502EEfc", "data": "0x70a08231000000000000000000000000c94770007dda54cf92009bff0de90c06f603a09f"}, "0x62ff07"], "id": 7}'

Where 0x62ff07 was the current block in that moment (now, of course, it is more than 12 blocks before the current).


{"jsonrpc":"2.0","id":7,"error":{"code":-32002,"message":"project ID does not have access to archive state","data":{"see":""}}}

Thank you,


Hi acuesta welcome to the Infura Community!

This issue was due to the Ropsten fork that occurred yesterday, you should no longer be seeing the requirement for archive when sending those requests.

1 Like

me to. You know why?

1 Like

Hi @ant9527 - this may be due to the Ropsten re-org and fork that occurred yesterday. We’re still seeing intermittent instability with Ropsten, so I’d suggest trying a different network for the time being.

I just tested it now and still got the error on ropsten… Just realized I replied to a comment in 2019 lol

Hi @Ace_Cal there was a very significant re-org on Ropsten this weekend that caused network wide issues. We reported this here,

Are you still experiencing issues?

Nope all good, thanks