Ethereum RPC endpoints: free public URLs and private API-key providers by latency
RPCsAlchemy
Trails34 ms
- rank
- #4
GetBlock
Leads10 ms
- rank
- #1
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 23 ms | 8 ms |
| EU-West | 53 ms | 16 ms |
| Singapore | 26 ms | 5 ms |
Alchemy leads on 1 of 9 shared benchmarks, GetBlock on 8. Alchemy wins on Hyperliquid RPC endpoints (34 ms vs 83 ms). GetBlock wins on Ethereum RPC endpoints (10 ms vs 34 ms), Arbitrum RPC endpoints (8 ms vs 34 ms), Base RPC endpoints (9 ms vs 33 ms), BNB Chain RPC endpoints (9 ms vs 35 ms). Data as of 2026-09-30 UTC.
Web3 infrastructure provider offering NFT API, RPC nodes, and blockchain data APIs. Multi-chain EVM coverage.
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.
Alchemy
Trails34 ms
GetBlock
Leads10 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 23 ms | 8 ms |
| EU-West | 53 ms | 16 ms |
| Singapore | 26 ms | 5 ms |
Alchemy
Trails34 ms
GetBlock
Leads8 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 24 ms | 12 ms |
| EU-West | 52 ms | 10 ms |
| Singapore | 26 ms | 3 ms |
Alchemy
Trails33 ms
GetBlock
Leads9 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 22 ms | 9 ms |
| EU-West | 49 ms | 11 ms |
| Singapore | 27 ms | 6 ms |
Alchemy
Trails35 ms
GetBlock
Leads9 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 24 ms | 13 ms |
| EU-West | 53 ms | 10 ms |
| Singapore | 29 ms | 4 ms |
Alchemy
Trails33 ms
GetBlock
Leads9 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 24 ms | 13 ms |
| EU-West | 49 ms | 10 ms |
| Singapore | 27 ms | 4 ms |
Alchemy
Trails33 ms
GetBlock
Leads9 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 23 ms | 13 ms |
| EU-West | 51 ms | 10 ms |
| Singapore | 26 ms | 3 ms |
Alchemy
Leads34 ms
GetBlock
Trails83 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 22 ms | 235 ms |
| EU-West | 54 ms | 10 ms |
| Singapore | 27 ms | 3 ms |
Alchemy
Trails31 ms
GetBlock
Leads11 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 18 ms | 12 ms |
| EU-West | 44 ms | 11 ms |
Alchemy
Trails39 ms
GetBlock
Leads14 ms
Per region
| Region | Alchemy | GetBlock |
|---|---|---|
| US-East | 26 ms | 13 ms |
| EU-West | 53 ms | 16 ms |
Alchemy and GetBlock are compared on 9 shared OpenChainBench benchmarks. Alchemy leads on Hyperliquid RPC endpoints. GetBlock leads on Ethereum RPC endpoints. See the live table on this page for every metric.
On the Hyperliquid RPC endpoints benchmark, Alchemy leads at 34 ms versus GetBlock at 83 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.