PublicNode leads on all 3 live benchmarks. PublicNode wins on Fastest free Kava RPC, live no-key EVM endpoint latency (87 ms vs 657 ms), Fastest free Metis RPC, live no-key EVM endpoint latency (86 ms vs 664 ms), Fastest free Arbitrum Nova RPC, live no-key EVM endpoint latency (87 ms vs 639 ms).
Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.
ThirdWeb operates a keyless public RPC gateway at `<chainid>.rpc.thirdweb.com` covering 2000+ EVM chains via chain-id routing. Free tier is rate-limited per IP with no signup; paid tiers unlock higher throughput and dedicated endpoints. Used keyless across 13 chains on the RPC latency cluster (arbitrum, ethereum, polygon, optimism, base, bnb, avalanche, linea, worldchain, kaia, ink, opbnb + more).
PublicNode
Leads87 ms
thirdweb
Trails657 ms
Per region
| Region | PublicNode | thirdweb |
|---|---|---|
| US-East | 88 ms | 689 ms |
| EU-West | 86 ms | 641 ms |
| Singapore | 87 ms | 643 ms |
PublicNode
Leads86 ms
thirdweb
Trails664 ms
Per region
| Region | PublicNode | thirdweb |
|---|---|---|
| US-East | 84 ms | 650 ms |
| EU-West | 89 ms | 672 ms |
| Singapore | 85 ms | 670 ms |
PublicNode
Leads87 ms
thirdweb
Trails639 ms
Per region
| Region | PublicNode | thirdweb |
|---|---|---|
| US-East | 88 ms | 627 ms |
| EU-West | 87 ms | 639 ms |
| Singapore | 85 ms | 652 ms |
PublicNode and thirdweb are compared on 3 shared OpenChainBench benchmarks. PublicNode leads on Fastest free Kava RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.
On the Fastest free Kava RPC, live no-key EVM endpoint latency benchmark, PublicNode leads at 87 ms versus thirdweb at 657 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.