Why do I see a Free tier error when calling eth_getLogs with a large block range?
Last updated: August 25, 2026
The eth_getLogs method applies a block range limit that depends on your plan tier. On the Free tier, this limit is small, so a request with a wider block range fails with an error referencing the Free tier restriction.
Upgrading to the Pay As You Go (PAYG) plan raises this limit substantially for most major chains, but it does not remove the limit entirely. On PAYG, a request to eth_getLogs on most major chains succeeds if it either stays within a 10,000 block range with no cap on response size, or spans any wider block range as long as the response contains 10,000 logs or fewer (and stays under the general 150MB response size cap). A request that satisfies neither condition is rejected, even on PAYG.
The Enterprise plan can raise the block range limit further on some chains, though the exact limit still varies by chain. Contact support@alchemy.com if you need the current limit for a specific chain on your plan.
How to upgrade
Go to Billing Settings in the Alchemy Dashboard.
Select the Pay As You Go plan. PAYG has no upfront commitment, and you're billed based on compute unit usage. See Alchemy Pricing for current rates.
Once the upgrade takes effect, your
eth_getLogsrequests follow the PAYG block range and response size limits described above instead of the smaller Free tier restriction.
For billing or invoice questions, contact billing@alchemy.com.