Docs
PricingDashboard

Platform errors

Unknown endpoint lock

When clients hammer non-UUID paths or unknown endpoint UUIDs, RpcNode may temporarily lock the client IP. This uses the same JSON-RPC code -32005 as RPS limits but a different message: too many unknown endpoint requests.

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": "too many unknown endpoint requests"
  }
}

Causes

  • Brute-forcing or scanning UUID paths.
  • Misconfigured client retrying a deleted / wrong endpoint UUID.
  • Health checks hitting / without a valid UUID path.

How to fix

  • Use the exact UUID from the dashboard; stop retrying 404 endpoint not found in a tight loop.
  • Wait until the lock expires (response may include lock-until style headers), then retry with the correct URL.
  • Do not share or log full endpoint URLs in public CI logs.

Related