How to stop Solana RPC 429 errors (Too Many Requests)

A 429 from a Solana RPC means you sent more requests per second than your plan allows. It always arrives at the worst time, because your bot is busiest exactly when the market is. Here is what is going on and how to make it stop.

Where 429s come from

What actually fixes it

  1. Space your requests. If the plan allows 10 a second, send one every 100 ms, not ten at once.
  2. Use more than one endpoint. Two keys at 10 a second are 20 a second, and when one refuses, the other is still there.
  3. Back off the endpoint, not the request. When an endpoint refuses, rest that endpoint (honouring Retry-After if it sends one) and send the call somewhere else straight away.
  4. Batch. getMultipleAccounts reads 100 accounts in one request. A JSON-RPC batch sends several calls in one HTTP request.
  5. Do not retry real errors. "Invalid param" will be invalid on every endpoint. Retrying it only burns quota.

Working code

solana-rpc-pool does those five things, with no dependencies:

import { createPool } from "solana-rpc-pool";

const rpc = createPool({
  endpoints: [
    { url: "https://rpc-one.example/?api-key=KEY_ONE", rps: 10 },
    { url: "https://rpc-two.example/?api-key=KEY_TWO", rps: 10 },
  ],
});

const slot = await rpc.call("getSlot");
const [epoch, height] = await rpc.batch([["getEpochInfo"], ["getBlockHeight"]]);
console.table(rpc.stats());   // calls, errors, rate-limit hits and latency per endpoint

Each endpoint gets its own rate. A 429, 403, 5xx or timeout rests that endpoint for 1 s, 2 s, 4 s, up to a minute, and the call moves to the next one. The public endpoint is used only as a last resort. Endpoints are named by host in errors and stats, so an API key never ends up in a log.

A note on keys

Using several keys is normal across providers or across projects you own. Check each provider's terms before stacking many free accounts with one of them.

When this is not enough

If you are polling the same data in a loop, a WebSocket subscription costs far less than repeated HTTP calls. See solana-ws-keepalive.

Want it done for you?

This is the small, open version. Blix is the AI-powered Solana memecoin terminal it comes from: every pump.fun launch live, AI coin ratings, narratives, wallet and X tracking, and one-click trading with 0% fees. There is a public API and an MCP server too.

Start trading on BlixJoin the Discord

Help build it

solana-rpc-pool is open source and takes pull requests. There are good first issues with step-by-step instructions, and setup is git clone and npm test.

More guides

How to get a pump.fun token's market cap and bonding curve progress without an APIpump-curveHow to detect new pump.fun tokens in real time (and stream every trade)pump-streamHow to calculate a Solana token's top 10 holders percentage (and why explorers overstate it)sol-holdersHow to parse a Solana swap transaction for any DEXsolana-swap-parserWhy your Solana WebSocket stops receiving messages, and how to keep it alivesolana-ws-keepalive