Docs
PricingDashboard

Platform errors

RPS rate limit exceeded

Each RpcNode endpoint has a fixed requests-per-second (RPS) limit from your plan. When the limit is exceeded within a one-second window, the gateway rejects the request before it reaches the upstream node.

HTTP 429-32005

← All errors

Example response

Example

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32005,
    "message": "rps limit exceeded"
  }
}

Causes

  • Burst traffic above the endpoint RPS (counter resets every Unix second).
  • Multiple workers or clients sharing one endpoint UUID.
  • Retries without backoff that amplify load in the same second.

How to fix

  • Spread requests across time or add client-side rate limiting under your plan RPS.
  • Upgrade the plan for a higher RPS limit (shown in the dashboard and on pricing).
  • Create separate endpoints if you need isolated quotas per app or environment.
  • Back off on HTTP 429 / -32005 before retrying.

Notes

  • Rejected RPS requests do not consume credits and are not counted in usage statistics.
  • A related -32005 message, "too many unknown endpoint requests", is returned when probing invalid or unknown endpoint UUIDs too aggressively (abuse protection). That is not your plan RPS — fix the URL / UUID first.

Abuse lock on unknown endpoints

If the path UUID is invalid or the endpoint does not exist and the client keeps retrying, the gateway may temporarily lock the client IP and return HTTP 429 with -32005 and message "too many unknown endpoint requests". Response headers may include lock metadata.

Example

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32005,
    "message": "too many unknown endpoint requests"
  }
}

Related