RPC nodes

RPC Node Benchmarks

Every free, no-key public RPC endpoint, measured per chain with the same probe: one identical eth_blockNumber call every 15 seconds from 3 regions (N. Virginia, Amsterdam, Singapore). The matrix below folds the per-chain leaderboards into one view — fastest provider per chain, fastest per region, and which gateway covers your whole multichain stack. Headline numbers are 24h p50 round-trip latency; methodology and exclusion rules live on the parent rpc-capabilities benchmark.

Chains benched

10

Unique providers

15

Probe regions

3

Fastest provider overall

Cloudflare · 19 ms

10 of 10 chains · 24h p50, 3 probe regions

#Chain::Fastest provider^US-East::EU-West::Singapore::Providers::24h trend
1Ethereum logoEthereumCloudflare logoCloudflare19 ms9 msTenderly21 msPublicNode9 msCloudflare9
2BNB Chain logoBNB ChaindRPC logodRPC22 ms5 msBinance18 msPublicNode11 msdRPC5
3Polygon PoS logoPolygon PoSdRPC logodRPC22 ms11 msPublicNode17 msPublicNode13 msdRPC5
4Base logoBasedRPC logodRPC22 ms10 msPublicNode20 msPublicNode12 msdRPC6
5Arbitrum One logoArbitrum OnedRPC logodRPC22 ms11 msTenderly17 msPublicNode13 msdRPC8
6Linea logoLineadRPC logodRPC23 ms9 msPublicNode18 msPublicNode14 msdRPC4
7Scroll logoScrolldRPC logodRPC23 ms10 msPublicNode17 msPublicNode16 msdRPC4
8Avalanche logoAvalanchedRPC logodRPC24 ms9 msPublicNode20 msPublicNode13 msdRPC6
9Mantle logoMantledRPC logodRPC24 ms11 msPublicNode20 msPublicNode13 msdRPC4
10Optimism logoOptimismdRPC logodRPC24 ms10 msPublicNode20 msPublicNode12 msdRPC6

Source: the open-source rpc-capabilities harness, one probe fleet per chain. Click a chain row for the full per-chain leaderboard with region tabs, success-rate classification and archive-depth audits; click a provider for its product page. Refresh interval 60s.

Methodology

Each chain row aggregates that chain's dedicated bench: an identical JSON-RPC POST (eth_blockNumberor the chain's equivalent head call) sent every 15 seconds to every free, no-key public endpoint from us-east, eu-west and Singapore. Headline figures are the 50th percentile of client-side round-trip latency over the trailing 24 hours, averaged across the three probe origins; per-region columns re-scope the same percentile to a single origin. Responses are classified (ok / http_err / jsonrpc_err / stale / timeout) so a fast error message never ranks as fastest. Providers that key-gate, region-block or rate-limit below the probe cadence are excluded rather than listed with an asterisk.

Data and methodology released under CC BY 4.0. Reuse with attribution to OpenChainBench.