Ethereum RPC endpoints: free public URLs and private API-key providers by latency
RPCsChainstack
Trails33 ms
- rank
- #4
- samples
- 45provisional
GetBlock
Leads11 ms
- rank
- #2
- samples
- 45provisional
Chainstack leads on 5 of 16 shared benchmarks, GetBlock on 11. Chainstack wins on Base RPC endpoints (7 ms vs 10 ms), Hyperliquid RPC endpoints (52 ms vs 158 ms), Most requests a free RPC plan buys, across 13 providers (3.00M vs 75.0K), Fastest private Base WebSocket push, per-block race across keyed RPC providers (1.19% vs 0.23%). GetBlock wins on Ethereum RPC endpoints (11 ms vs 33 ms), Arbitrum RPC endpoints (11 ms vs 24 ms), BNB Chain RPC endpoints (12 ms vs 19 ms), Polygon RPC endpoints (12 ms vs 30 ms). Data as of 2026-11-15 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
Trails33 ms
GetBlock
Leads11 ms
Chainstack
Trails24 ms
GetBlock
Leads11 ms
Chainstack
Leads7 ms
GetBlock
Trails10 ms
Chainstack
Trails19 ms
GetBlock
Leads12 ms
Chainstack
Trails30 ms
GetBlock
Leads12 ms
Chainstack
Trails32 ms
GetBlock
Leads20 ms
Chainstack
Leads52 ms
GetBlock
Trails158 ms
Chainstack
Trails38 ms
GetBlock
Leads14 ms
Chainstack
Trails20 ms
GetBlock
Leads16 ms
Chainstack
Trails$198
GetBlock
Leads$150
Published prices, not invoices. Each figure is human-verified against the provider's own pricing page or API and carries the date it was read; the harness re-hashes 20 of those pages on a loop to catch an upstream edit. A 30-day month and flat traffic are assumed, the most generous reading. NOWNodes prices in EUR. A provider absent from a cell is not missing data: it has no plan that can serve that workload, usually a cap or a throughput ceiling rather than the price.
Chainstack
Leads3.00M
GetBlock
Trails75.0K
Allowance, not latency and not reliability. A plan that buys the most requests is not thereby the fastest or the most correct; those are measured on the per-chain RPC pages. Published allowances, human-verified against each provider's own pricing page with the date it was read. A free plan is one that costs nothing and renews, so Quicknode's one-month trial is not here. Where a provider publishes a daily cap it is multiplied by 30.
Chainstack
No data in window
GetBlock
Leads18.3 %
Chainstack
Leads1.19 %
GetBlock
Trails0.23 %
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 2.19% | 0.0028% |
| EU-West | 1.36% | 0.20% |
| Singapore | 0.0097% | 0.48% |
Chainstack
Trails2.04 %
GetBlock
Leads4.33 %
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 3.83% | 2.93% |
| EU-West | 0.12% | 1.23% |
| Singapore | 2.17% | 8.83% |
Chainstack
Trails0.63 %
GetBlock
Leads12.0 %
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 1.83% | 16.8% |
| EU-West | 0.010% | 12.6% |
| Singapore | 0.042% | 6.47% |
Chainstack
Trails5.48 %
GetBlock
Leads63.4 %
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| EU-West | 1.52% | 63.4% |
Chainstack
Leads18.9 %
GetBlock
Trails9.11 %
Per region
| Region | Chainstack | GetBlock |
|---|---|---|
| US-East | 56.3% | 18.2% |
Chainstack and GetBlock are compared on 17 shared OpenChainBench benchmarks. Chainstack leads on Base RPC endpoints. GetBlock leads on Ethereum RPC endpoints. See the live table on this page for every metric.
On the Base RPC endpoints benchmark, Chainstack leads at 7 ms (provisional) versus GetBlock at 10 ms (provisional). 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.