NOWNodes vs PublicNode 2026: 4 live benchmarks compared

Name: NOWNodes vs PublicNode OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

OpenChainBench

NOWNodes vs PublicNode

PublicNode leads on all 4 live benchmarks. PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (83 ms vs 211 ms), Ethereum RPC endpoints (74 ms vs 111 ms), BNB Chain RPC endpoints (75 ms vs 153 ms), Bitcoin RPC endpoints (75 ms vs 291 ms). Data as of 2026-10-11 UTC.

Read methodology Last measured Sun, 11 Oct 2026 02:13:50 UTCWindow: rolling 24h5 shared benchmarks, 4 measured on both sides

NOWNodes

Multi-chain node provider covering 110+ blockchains. Key-based REST and WebSocket RPC plus block explorers, with keyless public endpoints on a handful of chains (Ethereum, BNB, Bitcoin) rate-limited to 5 requests per second.

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

Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (plus Solana and Polkadot)

RPCs

NOWNodes

Trails

211 ms

p99: 747 ms
rank: #11
samples: 21,590

PublicNode

Leads

83 ms

p99: 256 ms
rank: #2
samples: 310,963

Per chain · per region

Chain	Provider	US-East	EU-West	Singapore	Aggregate
Ethereum	NOWNodes	108 ms	21 ms	204 ms	111 ms
Ethereum	PublicNode	16 ms	23 ms	182 ms	74 ms
BNB Chain	NOWNodes	139 ms	72 ms	249 ms	153 ms
BNB Chain	PublicNode	16 ms	23 ms	185 ms	75 ms

RPC latency

NOWNodesn/aPublicNoden/a

Latency is conditional on success: the harness times only calls returning a valid fresh block, so a mostly-failing endpoint can post a fast p50. Rows below 50 percent success are degraded; unresponsive probes pin below the table. The All chains aggregate favours single-chain foundation endpoints (Base, Binance, Arbitrum, Optimism, Avalanche officials) since they rank on one chain only; use a chain tab for honest comparison. Dead endpoints (cloudflare-eth POST returns -32603) are excluded.

Ethereum RPC endpoints: free public URLs and private API-key providers by latency

RPCs

NOWNodes

Trails

111 ms

p99: 543 ms
rank: #4
samples: 4,316

PublicNode

Leads

74 ms

p99: 239 ms
rank: #2
samples: 4,318

Per region

Region	NOWNodes	PublicNode
US-East	108 ms	16 ms
EU-West	21 ms	23 ms
Singapore	204 ms	182 ms

RPC latency

NOWNodesn/aPublicNoden/a

BNB Chain RPC endpoints: free public URLs and private API-key providers by latency

RPCs

NOWNodes

Trails

153 ms

p99: 816 ms
rank: #3
samples: 4,321

PublicNode

Leads

75 ms

p99: 204 ms
rank: #2
samples: 4,317

Per region

Region	NOWNodes	PublicNode
US-East	139 ms	16 ms
EU-West	72 ms	23 ms
Singapore	249 ms	185 ms

RPC latency

NOWNodesn/aPublicNoden/a

Coreum RPC endpoints: free public URLs by latency

RPCs

NOWNodes

No data in window

PublicNode

Trails

82 ms

p99: 291 ms
rank: #1
samples: 4,319

RPC latency

NOWNodesn/aPublicNoden/a

Bitcoin RPC endpoints: free public URLs by latency

RPCs

NOWNodes

Trails

291 ms

p99: 814 ms
rank: #3
samples: 4,320

PublicNode

Leads

75 ms

p99: 220 ms
rank: #1
samples: 4,320

Per region

Region	NOWNodes	PublicNode
US-East	164 ms	18 ms
EU-West	96 ms	22 ms
Singapore	613 ms	185 ms

RPC latency

NOWNodesn/aPublicNoden/a

Frequently asked questions

NOWNodes vs PublicNode: which one is better?

NOWNodes and PublicNode are compared on 5 shared OpenChainBench benchmarks. PublicNode leads on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains. See the live table on this page for every metric.

Which is faster, NOWNodes or PublicNode?

On the Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains benchmark, PublicNode leads at 83 ms versus NOWNodes at 211 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the NOWNodes 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.