RPC failover benchmark

How often Ethereum RPC calls succeed when an upstream returns HTTP 429 or 502, and how long requests take to finish. The controlled test and production observations measure different environments.

Controlled comparison

Measured UTC on darwin/arm64 with Atlas revision 54e0881f. Each row covers 100 simulated Ethereum mainnet eth_call requests in a local, single-process test.

Controlled Ethereum RPC failover measurements
SetupFirst upstreamSucceeded / totalp95 responsep99 responsep95 recovery
Single upstreamHTTP 4290 / 10011.04 ms11.7 ms—
Sequential two-upstream fallbackHTTP 429100 / 10032.07 ms33.77 ms21.04 ms
RouteMesh AtlasHTTP 429100 / 10032.67 ms35.73 ms21.49 ms
Single upstreamHTTP 5020 / 10011.03 ms11.04 ms—
Sequential two-upstream fallbackHTTP 502100 / 10032.05 ms32.58 ms21.03 ms
RouteMesh AtlasHTTP 502100 / 10032.3 ms33.82 ms21.23 ms

Production observations

Ethereum mainnet HTTP eth_call batches from to UTC. The first recorded upstream attempt returned HTTP 429 or 502.

Production Ethereum RPC responses after upstream errors
StrategyBatchesSuccess rateSucceeded via another providerRouter regionsp95 responsep99 response
economy13,19498.98%11,4733702.7 ms1,222.1 ms
performance11398.23%111297 ms460 ms

Methodology

In the controlled test, the primary returns an error after a scripted 10 ms delay, and the backup returns a valid response after 20 ms. We run the Atlas request coordinator with those same simulated upstreams and compare it with a single call and a sequential retry. Response percentiles include errors. Recovery measures time from the first error to a successful response and is reported only for successful requests. Timing includes local process scheduling. There are no network or provider latency measurements in this test.

The production snapshot covers one complete UTC hour after at least one hour of telemetry ingestion and counts each recorded batch ID once. It includes strategies with at least 100 qualifying batches. Success means the batch was fulfilled with a 2xx HTTP status and no JSON-RPC error. The alternate provider column counts successful batches whose selected provider differs from the first attempted provider. Response latency includes all outcomes and measures time at the router, excluding client network transit. Attempts can overlap, so the production data describes observed outcomes rather than the incremental time or effect of a retry.