Docs
PricingDashboard

Platform errors

Upstream unavailable

After auth and RPS checks, RpcNode forwards to one or more upstream full nodes with failover. If every candidate fails (connection error, non-forwardable status, or deadline), the gateway returns -32002 upstream unavailable.

HTTP 502-32002

← All errors

Example response

Example

HTTP/1.1 502 Bad Gateway
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": null,
  "error": {
    "code": -32002,
    "message": "upstream unavailable"
  }
}

Causes

  • All upstream candidates in the pool failed or timed out within UpstreamTimeout.
  • Upstream pool empty / not configured for the environment (related -32000 messages before forward).
  • Transient network or node process issues on the provider side.

How to fix

  • Retry with exponential backoff — many failures are transient.
  • Check RpcNode status / dashboard; if only one network fails, inspect that network page.
  • Reduce oversized eth_getLogs / heavy debug_* calls that may hit upstream timeouts (see family pages).

Notes

  • Related platform messages before forward: upstream pool unavailable, upstream not configured, method catalog unavailable, ratelimit unavailable (all -32000 with HTTP 502).
  • Successful upstream JSON-RPC error objects (e.g. execution reverted) are proxied as-is with the upstream HTTP status — they are not rewritten to -32002.

Related