Docs
PricingDashboard

Platform errors

Request timeouts

The gateway wraps upstream forwarding in a timeout (UpstreamTimeout). When the deadline expires while trying candidates, failover stops and clients see the same -32002 upstream unavailable response as other forward failures. There is no distinct JSON-RPC “timeout” code today.

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

  • Heavy methods (wide eth_getLogs, debug_trace*, large getblock verbosity) that exceed the forward deadline.
  • Upstream node under load or unreachable so all failover attempts burn the budget.
  • Very large batches processed as a single upstream round-trip.

How to fix

  • Narrow filters and block ranges; prefer smaller pages of results.
  • Split batches; avoid combining many heavy methods in one request.
  • Retry transient -32002 with backoff; persistent timeouts on one method usually mean the call is too heavy for a full-node SLA.

Related