Fastest Ethereum WebSocket newHeads push, live block-push lag across RPC providers
RPCsOnFinality
No data in window
PublicNode
Trails0.4 ms
- p99
- 10.24 s
- rank
- #1
- samples
- 28,479
OnFinality leads on all 4 live benchmarks. OnFinality wins on Polkadot RPC endpoints (53 ms vs 86 ms), Kusama RPC endpoints (53 ms vs 90 ms), Peaq Network RPC endpoints (55 ms vs 87 ms), Sui RPC endpoints (76 ms vs 80 ms). Data as of 2026-10-14 UTC.
Multi-chain infrastructure provider. Public keyless endpoints on 80+ networks with generous daily limits, plus dedicated and API-key tiers.
Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.
OnFinality
No data in window
PublicNode
Trails0.4 ms
OnFinality
Leads53 ms
PublicNode
Trails86 ms
Per region
| Region | OnFinality | PublicNode |
|---|---|---|
| US-East | 5 ms | 43 ms |
| EU-West | 90 ms | 33 ms |
| Singapore | 64 ms | 183 ms |
OnFinality
Leads53 ms
PublicNode
Trails90 ms
Per region
| Region | OnFinality | PublicNode |
|---|---|---|
| US-East | 6 ms | 46 ms |
| EU-West | 90 ms | 30 ms |
| Singapore | 63 ms | 194 ms |
OnFinality
Leads55 ms
PublicNode
Trails87 ms
Per region
| Region | OnFinality | PublicNode |
|---|---|---|
| US-East | 7 ms | 51 ms |
| EU-West | 95 ms | 24 ms |
| Singapore | 63 ms | 185 ms |
OnFinality
Leads76 ms
PublicNode
Trails80 ms
Per region
| Region | OnFinality | PublicNode |
|---|---|---|
| US-East | 10 ms | 31 ms |
| EU-West | 95 ms | 25 ms |
| Singapore | 122 ms | 182 ms |
OnFinality and PublicNode are compared on 5 shared OpenChainBench benchmarks. OnFinality leads on Polkadot RPC endpoints. See the live table on this page for every metric.
On the Polkadot RPC endpoints benchmark, OnFinality leads at 53 ms versus PublicNode at 86 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.