Even though the nodes deployed with Chainstack are not rate-limited or throttled down as per the articles Node and connection limitations, we still impose a soft limit on the requests per second (RPS) to prevent abuse of our system and ensure that all users have equal access to the available resources.

Exceeding this limit will result in a 429 Error,429 Client Error: Too Many Requests

You'll be able to view these errors or logs on your Node Metrics (Project > Node > endpoint-name-example )

It's important to note that batching also counts as RPS because each request is counted individually.

Preventing the error

You can deal with these 429 errors in many different ways:

1. Add a delay or timeout before a retry. Retry your request using increasing pauses in between.
2. Calculate beforehand how many RPS you'll be doing.
3. Use a third-party package to throttle based on a fixed number, such as:
   • https://pypi.org/project/ratelimit/
   • https://www.npmjs.com/package/axios-rate-limit
   • https://github.com/uber-go/ratelimit
4. Make sure to stay within our connection limitations as per our documentation on Node and connection limitations.