Ethereum RPC endpoints: free public URLs and private API-key providers by latency
RPCsGetBlock
Leads10 ms
- rank
- #1
QuickNode
Trails28 ms
- rank
- #2
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 8 ms | 30 ms |
| EU-West | 16 ms | 38 ms |
| Singapore | 5 ms | 16 ms |
GetBlock leads on 8 of 9 shared benchmarks, QuickNode on 1. GetBlock wins on Ethereum RPC endpoints (10 ms vs 28 ms), Arbitrum RPC endpoints (8 ms vs 29 ms), Base RPC endpoints (9 ms vs 28 ms), BNB Chain RPC endpoints (9 ms vs 27 ms). QuickNode wins on Hyperliquid RPC endpoints (28 ms vs 83 ms). Data as of 2026-09-30 UTC.
Multi-chain RPC provider covering 130+ networks, billed in Compute Units. Keyed JSON-RPC runs on shared nodes with the serving region selectable between New York, Frankfurt and Singapore. Cost is a chain multiplier times a method multiplier, with archive priced from an independent column rather than as a fixed surcharge.
Keyed RPC infrastructure across 30+ chains. Endpoint-scoped API tokens; free and paid plans are served from the same shared fleet, dedicated clusters on higher tiers.
GetBlock
Leads10 ms
QuickNode
Trails28 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 8 ms | 30 ms |
| EU-West | 16 ms | 38 ms |
| Singapore | 5 ms | 16 ms |
GetBlock
Leads8 ms
QuickNode
Trails29 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 12 ms | 30 ms |
| EU-West | 10 ms | 39 ms |
| Singapore | 3 ms | 17 ms |
GetBlock
Leads9 ms
QuickNode
Trails28 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 9 ms | 29 ms |
| EU-West | 11 ms | 37 ms |
| Singapore | 6 ms | 18 ms |
GetBlock
Leads9 ms
QuickNode
Trails27 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 13 ms | 29 ms |
| EU-West | 10 ms | 37 ms |
| Singapore | 4 ms | 13 ms |
GetBlock
Leads9 ms
QuickNode
Trails27 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 13 ms | 30 ms |
| EU-West | 10 ms | 37 ms |
| Singapore | 4 ms | 15 ms |
GetBlock
Leads9 ms
QuickNode
Trails21 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 13 ms | 30 ms |
| EU-West | 10 ms | 20 ms |
| Singapore | 3 ms | 15 ms |
GetBlock
Trails83 ms
QuickNode
Leads28 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 235 ms | 29 ms |
| EU-West | 10 ms | 37 ms |
| Singapore | 3 ms | 19 ms |
GetBlock
Leads11 ms
QuickNode
Trails33 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 12 ms | 30 ms |
| EU-West | 11 ms | 37 ms |
GetBlock
Leads14 ms
QuickNode
Trails33 ms
Per region
| Region | GetBlock | QuickNode |
|---|---|---|
| US-East | 13 ms | 30 ms |
| EU-West | 16 ms | 37 ms |
GetBlock and QuickNode are compared on 9 shared OpenChainBench benchmarks. GetBlock leads on Ethereum RPC endpoints. QuickNode leads on Hyperliquid RPC endpoints. See the live table on this page for every metric.
On the Ethereum RPC endpoints benchmark, GetBlock leads at 10 ms versus QuickNode at 28 ms. Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing; panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.