Ethereum RPC endpoints: free public URLs and private API-key providers by latency
RPCsChainstack
Trails32 ms
- rank
- #3
GetBlock
Leads10 ms
- rank
- #1
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 19 ms | 8 ms |
| EU-West | 47 ms | 16 ms |
| Singapore | 30 ms | 5 ms |
GetBlock leads on all 9 live benchmarks. GetBlock wins on Ethereum RPC endpoints (10 ms vs 32 ms), Arbitrum RPC endpoints (8 ms vs 115 ms), Base RPC endpoints (9 ms vs 34 ms), BNB Chain RPC endpoints (9 ms vs 31 ms). Data as of 2026-09-30 UTC.
Managed blockchain node platform. Deploys dedicated Global Nodes per chain with keyed HTTPS/WSS endpoints; free plan includes one node and 3M requests per month.
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.
Chainstack
Trails32 ms
GetBlock
Leads10 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 19 ms | 8 ms |
| EU-West | 47 ms | 16 ms |
| Singapore | 30 ms | 5 ms |
Chainstack
Trails115 ms
GetBlock
Leads8 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 36 ms | 12 ms |
| EU-West | 69 ms | 10 ms |
| Singapore | 242 ms | 3 ms |
Chainstack
Trails34 ms
GetBlock
Leads9 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 18 ms | 9 ms |
| EU-West | 54 ms | 11 ms |
| Singapore | 31 ms | 6 ms |
Chainstack
Trails31 ms
GetBlock
Leads9 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 17 ms | 13 ms |
| EU-West | 47 ms | 10 ms |
| Singapore | 27 ms | 4 ms |
Chainstack
Trails107 ms
GetBlock
Leads9 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 17 ms | 13 ms |
| EU-West | 54 ms | 10 ms |
| Singapore | 250 ms | 4 ms |
Chainstack
Trails36 ms
GetBlock
Leads9 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 34 ms | 13 ms |
| EU-West | 47 ms | 10 ms |
| Singapore | 27 ms | 3 ms |
Chainstack
Trails177 ms
GetBlock
Leads83 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 207 ms | 235 ms |
| EU-West | 74 ms | 10 ms |
| Singapore | 248 ms | 3 ms |
Chainstack
Trails34 ms
GetBlock
Leads11 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 20 ms | 12 ms |
| EU-West | 48 ms | 11 ms |
Chainstack
Trails46 ms
GetBlock
Leads14 ms
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 23 ms | 13 ms |
| EU-West | 69 ms | 16 ms |
Chainstack and GetBlock are compared on 9 shared OpenChainBench benchmarks. GetBlock leads on Ethereum RPC endpoints. See the live table on this page for every metric.
On the Ethereum RPC endpoints benchmark, GetBlock leads at 10 ms versus Chainstack at 32 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.