JUMPBIT
Open app
FixesUpdated 23 Oct 20261 min read

Solana RPC "429 Too Many Requests": limits and fixes

The fix

Your app or wallet sent more requests than the RPC endpoint allows. The public mainnet endpoint allows 100 requests per 10 seconds per IP, 40 per 10 seconds for a single method and 40 concurrent connections.

Tools covered

  1. HeliusSolana infrastructure provider offering RPC nodes, APIs, LaserStream gRPC, webhooks and Sender.UpVisit
  2. QuickNodeBlockchain RPC and API provider with tiered plans from $49/month and Solana gRPC on higher tiers.UpVisit
  3. Triton OneSolana RPC, streaming and ledger infrastructure provider, pay-as-you-go from a $125 minimum deposit.UpVisit

What the error means

429 Too Many Requests

Your app or wallet sent more requests than the RPC endpoint allows. The public mainnet endpoint allows 100 requests per 10 seconds per IP, 40 per 10 seconds for a single method and 40 concurrent connections.

Where it comes fromRPC provider (HTTP)
CodeHTTP 429

How to fix it

  1. Switch to a dedicated RPC provider; the public endpoints are not intended for production.
  2. Batch or cache reads instead of polling every account separately.
  3. Back off and retry after a short delay.

If that is not it

  • If you already use a paid RPC, check your plan's requests-per-second limit.

More fixes: how to decode any Solana error code and why Solana transactions fail.

Source

Error text and code from Solana clusters documentation, read on 24 October 2026.

Questions people ask

What are the Solana public RPC limits?

100 requests per 10 seconds per IP, 40 per 10 seconds for one method, 40 concurrent connections and 100 MB per 30 seconds.

Which RPC should I use instead?

Compare plans on the [RPC page](/en/resources/tools/c/rpc), for example [Helius vs QuickNode](/en/resources/compare/helius-vs-quicknode).

Solana RPC "429 Too Many Requests": limits and fixes | Jumpbit