429 Errors Response Information

Chainstack nodes have a soft limit on the requests per second (RPS) that you can make to them. This is to prevent abuse and ensure fair resource allocation. If you exceed this limit, you will get a 429 Error, which means Too Many Requests.

You can find all of your limitations mentioned here:

https://docs.chainstack.com/docs/limits

Check your Node Metrics

You can see the errors and logs on your Node Metrics page in the Chainstack platform. 

Go to Project > Node > endpoint-name-example to access it. You can also see the RPS limit for your node there.

429 errors in your debug logs

If you see HTTP 429 Errors in your debug log, but none appear in your Chainstack Dashboard — the issue must come from between the endpoint and you. 

For example, there is a known issue with Solana Python SDK causing such HTTP 429 errors. We recommend switching to another library, which should help to mitigate your errors.

Reduce your RPS

If you actually see 429 errors on your dashboard it means you indeed hit the RPS limitations. There are several ways to reduce your RPS and avoid the 429 Error:

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.
5. You can also find more specific limits, such as Solana limits on this documentation page.
   
   

Conclusion

By understanding the error root cause and reducing your RPS, you can prevent the 429 Error and use your Chainstack node smoothly.

If you have any further questions or concerns, please feel free to contact Chainstack Support with any questions by emailing support@chainstack.com or submitting this form.