AlternativesSourced from Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (plus Solana and Polkadot)
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.
Positioning
dRPC is a routing layer, not a node operator. Every request lands on Dproxy, which scores third-party providers on health, capability, location, and recent compute-unit distribution; the request is then handed to Dshackle, an open-source fault-tolerant load balancer that picks the specific upstream node based on the method called, the current chain head, and the block context required. The routing is method-aware: a sendRawTransaction fans out to every capable node, a balance read routes only to lag-free upstreams, and a historical read filters to nodes that have synced to the requested block. This is architecturally distinct from single-operator RPCs, where a request runs against one homogeneous fleet, and distinct from public free RPCs, which have no cross-provider selection at all. For the rpc-capabilities axis, the routing model directly shapes the observed method coverage: a method that any upstream supports counts as covered network-wide, and uptime aggregates across upstreams rather than depending on any one operator's incident window. Chain coverage spans 120+ chains across 217 networks (Chainlist product) spanning EVM L1s and L2s, Solana, Bitcoin, Cosmos, and TON. The typical use case is teams that want one endpoint per chain with automatic failover; migration happens when a team needs a proprietary method only one upstream exposes.
About dRPC: drpc.org
Top 5 dRPC alternatives
- Best
- 75 ms
- Median
- 266 ms
- Worst
- 716 ms
- Spread
- 7.8×218 ms → 1.70 s
- Samples · 24h
- 470,84813 providers
RPC latency · last 24 hours
RPC latency · last 24 hours
Region
Show
Product ledger · sorted by p50
| Product | p50 | Trend | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Color | № | 24h | ||||||||
| 01 | 75 ms | |||||||||
| 02 | 161 ms | |||||||||
| 03 | 182 ms | |||||||||
| 04 | 195 ms | |||||||||
| 05 | 247 ms | |||||||||
| 06 | 254 ms | |||||||||
| 07 | 266 ms | |||||||||
| 08 | 269 ms | |||||||||
| 09 | 277 ms | |||||||||
| 10 | 304 ms | |||||||||
| 11 | 333 ms | |||||||||
| 12 | 716 ms | |||||||||
| — | — | — | ||||||||
Same data as /benchmarks/rpc-capabilities, refreshed every minute. OpenChainBench is community-run; methodology is open.