Rate Limits

We set rate limits on all our nodes to protect nodes from abusive traffic. Our goal is that human users have a good experience without the annoyance of bad bots.

Rate limits are applied based on IP and other parameters. If you hit a rate limit, you will get a 429 HTTP response code. If you repeatedly hit our rate limits, you may see Connection refused errors. This means that our firewalls have temporarily blocked you.

If you see a 429 error, your code should back off and reduce the rate of requests to avoid any temporary banning of your IP.

The default rate limit on our shared service is 1200 requests per 10 seconds for a single method call. Many methods, like getProgramAccounts, have much lower rate limits. However, all rate limits are suitable for a well-written front-end application.

We can adjust the rate limits for dedicated nodes per your needs.

To see the overall rate limits applied to your endpoint, visit https://<endpoint>.rpcpool.com/ratelimits . For shared pools, we also provide HTTP headers X-Ratelimit-XYZin the HTTP responses.