Max Rate Limit Reached error thrown by Etherscan
See original GitHub issueAfter upgrading to v5 ether balance checks and json rpc calls end up with the following error (This was not shown in v4) :
Rate limit reached for this call:
https://api.etherscan.io/api?module=proxy&action=eth_blockNumber&apikey=9D13ZE7XSBTJ94N9BNJ2MA33VMAY2YPIRB
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
API Key Rate Limit & Errors - Etherscan Information Center
The APIs are free for the community with a maximum rate limit of up to 5 calls per sec/IP with a valid API...
Read more >Always getting Max rate limit reached error on api : r/etherscan
Our rate limits are enforced based on API Key and not IP address, hence having other implementations running the same key will contribute...
Read more >etherscan request API limit [closed] - Ethereum Stack Exchange
The number of requests per second is limited to 5 request per second. There is not paid service yet. The Etherscan Ethereum Developer...
Read more >PSA for Developers: Implementation of API Key requirements ...
The Etherscan Developer APIs are designed to provide the Ethereum community with accessible and consistent Ethereum data. The APIs are provided as a ......
Read more >Documentation - Ethers.js
higher rate limit (since you are not using the shared rate limit) ... Sub-classes must implement this, however they may simply throw an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve added retry logic (with exponential back-off) to the Etherscan provider in v5.0.6, so I suspect this should be addressed? Please try it out and let me know.
I’ve noticed this starting today as well. It looks like Etherscan may have dialed up their throttling for the ethers default API key.
I’ll get in touch with them and look into this. It may need to be removed from the default provider for now.
Thanks!