OnFinality vs PublicNode

OnFinality leads on 3 of 5 shared benchmarks, PublicNode on 2. OnFinality wins on Fastest free Polkadot RPC, live no-key endpoint latency (56 ms vs 104 ms), Fastest free Kusama RPC, live no-key endpoint latency (53 ms vs 106 ms), Fastest free Peaq Network RPC, live no-key endpoint latency (53 ms vs 101 ms). PublicNode wins on Fastest Ethereum WebSocket newHeads push, live block-push lag across RPC providers (0.4 ms vs 253 ms), Fastest free Sui RPC, live no-key endpoint latency (91 ms vs 98 ms).

Read methodology Last measured Window: rolling 24h6 shared benchmarks
OnFinality logo
OnFinality

Multi-chain infrastructure provider. Public keyless endpoints on 80+ networks with generous daily limits, plus dedicated and API-key tiers.

PublicNode logo
PublicNode

Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.

Side by side measurements

Frequently asked questions

OnFinality vs PublicNode: which one is better?

OnFinality and PublicNode are compared on 6 shared OpenChainBench benchmarks. OnFinality leads on Fastest free Polkadot RPC, live no-key endpoint latency. PublicNode leads on Fastest Ethereum WebSocket newHeads push, live block-push lag across RPC providers. See the live table on this page for every metric.

Which is faster, OnFinality or PublicNode?

On the Fastest free Polkadot RPC, live no-key endpoint latency benchmark, OnFinality leads at 56 ms versus PublicNode at 104 ms. Live measurement is updated continuously by the OpenChainBench harness.

Which is faster, OnFinality or PublicNode?

On the Fastest Ethereum WebSocket newHeads push, live block-push lag across RPC providers benchmark, PublicNode leads at 0.4 ms versus OnFinality at 253 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the OnFinality vs PublicNode comparison measured?

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.

How this pair was selected

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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.