AlternativesSourced from Fastest free public RPC for Ethereum, BNB, Polygon and 7 more EVM chains
dRPC alternatives
Decentralized RPC mesh routing requests across third-party node providers
dRPC is a decentralized RPC mesh that routes each JSON-RPC request across third-party node providers with consensus checks, exposing a no-key public tier on every major EVM network. Picking a default endpoint for a dapp comes down to a per-chain question: which free public RPC is actually fast and reliable on the chain my product runs on, right now, not according to a marketing page. This benchmark answers it directly. The harness sends an identical `eth_blockNumber` POST every 15 seconds against 15 audited no-key public RPC providers across 10 EVM chains (Ethereum, Arbitrum, Base, Optimism, Avalanche, BNB, Polygon, Linea, Scroll, Mantle), from three Railway regions (us-east, eu-west, sgp). p50, p90 and p99 are computed via Prometheus `quantile_over_time` over the last 24 hours, and a five-class result label (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) lets the success-rate column catch endpoints that return HTTP 200 with a JSON-RPC error body (the Cloudflare-eth trap). An archive-depth probe runs every 5 minutes against five depths so a fast endpoint that silently serves pruned state is not ranked as a viable archive source. The cohort competing with dRPC includes PublicNode, 1RPC, MeowRPC, Tenderly Gateway, Nodies, Lava, Merkle, Flashbots Protect and Cloudflare, plus the chain-official foundation endpoints on Base, BNB, Arbitrum, Optimism and Avalanche. The chain tab filters every query so the leader is reported per network rather than as a cross-chain aggregate that rewards whichever single-chain endpoint happens to be fastest on its one chain.
About dRPC: drpc.org
Top 5 dRPC alternatives
- Best
- 25 ms
- Median
- 122 ms
- Worst
- 349 ms
- Spread
- 100.6×41 ms → 4.17 s
- Samples · 24h
- 492,47415 providers
RPC latency · last 24 hours
RPC latency · last 24 hours
Region
Show
Product ledger · sorted by p50
| Product | p50 | Trend | |||||||
|---|---|---|---|---|---|---|---|---|---|
| № | Name | p50 | 24h | ||||||
| 01 | 25 ms | ||||||||
| 02 | 28 ms | ||||||||
| 03 | 32 ms | ||||||||
| 04 | 70 ms | ||||||||
| 05 | 78 ms | ||||||||
| 06 | 116 ms | ||||||||
| 07 | 122 ms | ||||||||
| 08 | 122 ms | ||||||||
| 09 | 124 ms | ||||||||
| 10 | 126 ms | ||||||||
| 11 | 162 ms | ||||||||
| 12 | 165 ms | ||||||||
| 13 | 170 ms | ||||||||
| 14 | 183 ms | ||||||||
| 15 | 349 ms | ||||||||
Same data as /benchmarks/rpc-capabilities, refreshed every minute. OpenChainBench is community-run; methodology is open.