Rate Limits

Understand NoLimitNodes rate limits and plan-based quotas.

Limits apply by plan and product.

Plan limits

FeatureFreeProUltraMaxEnterprise
RPC requests3/sec200/sec500/sec1,000/secUnlimited (up to 100,000 rps depending on methods consumed)
sendTransaction1/sec50/sec200/sec400/sec200/sec
Concurrent WebSocket connectionsNone5203040
Yellowstone gRPC streamsNone2101520
Enhanced or Program StreamsNone2203040
Shredstream destinationsNoneNone112
Geyser plugin slotsNoneNoneNoneNone4
blockSubscribeNoneNoYesYesYes
InfrastructureSharedPrivatePrivatePrivateDedicated
SupportCommunityPriorityPriorityPriorityNamed
SLANonePlan termsPlan termsPlan termsContract

The WebSocket limit counts concurrent connections, not subscriptions. The gRPC stream limit is shared by the normal Yellowstone gRPC endpoint and the HyperStreams endpoint.

Enterprise has no fixed per-second cap. Throughput is bounded by the 16 reserved vCPU allocated to the account; heavier RPC methods consume more of that budget.

Check the pricing page and your dashboard for current commercial terms.

HTTP rate limits

The RPC endpoint returns HTTP 429 after your request rate exceeds its limit.

Retry with exponential backoff and jitter.

const wait = (ms) => new Promise((resolve) => setTimeout(resolve, ms)) async function callRpc(body, attempt = 0) {  const response = await fetch("https://rpc.mainnet.solana.nolimitnodes.com", {    method: "POST",    headers: {      "content-type": "application/json",      "x-api-key": process.env.NLN_API_KEY,    },    body: JSON.stringify(body),  })   if (response.status === 429 && attempt < 4) {    const delay = 250 * 2 ** attempt + Math.floor(Math.random() * 150)    await wait(delay)    return callRpc(body, attempt + 1)  }   return response.json()}

Connection limits

Close subscriptions after use. A disconnected client still needs server cleanup time.

Use one filtered Yellowstone subscription instead of many broad subscriptions where possible.

Reduce usage

  • Batch independent RPC reads.
  • Use getMultipleAccounts for grouped account reads.
  • Subscribe instead of polling.
  • Cache epoch and cluster metadata.
  • Share one backend subscription across browser users.
  • Remove stale filters before opening new streams.