PublicNode leads on all 4 live benchmarks. PublicNode wins on Kava RPC endpoints (65 ms vs 519 ms), Metis RPC endpoints (60 ms vs 509 ms), Arbitrum Nova RPC endpoints (61 ms vs 511 ms), 0G RPC endpoints (64 ms vs 517 ms). Data as of 2026-11-02 UTC.
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
Leads65 ms
thirdweb
Trails519 ms
Per region
| Region | PublicNode | thirdweb |
|---|---|---|
| US-East | 27 ms | 350 ms |
| EU-West | 34 ms | 584 ms |
| Singapore | 135 ms | 627 ms |
PublicNode
Leads60 ms
thirdweb
Trails509 ms
Per region
| Region | PublicNode | thirdweb |
|---|---|---|
| US-East | 30 ms | 321 ms |
| EU-West | 37 ms | 584 ms |
| Singapore | 114 ms | 622 ms |
PublicNode
Leads61 ms
thirdweb
Trails511 ms
Per region
| Region | PublicNode | thirdweb |
|---|---|---|
| US-East | 28 ms | 298 ms |
| EU-West | 39 ms | 595 ms |
| Singapore | 117 ms | 640 ms |
PublicNode
Leads64 ms
thirdweb
Trails517 ms
Per region
| Region | PublicNode | thirdweb |
|---|---|---|
| US-East | 32 ms | 351 ms |
| EU-West | 41 ms | 590 ms |
| Singapore | 118 ms | 610 ms |
PublicNode and thirdweb are compared on 4 shared OpenChainBench benchmarks. PublicNode leads on Kava RPC endpoints. See the live table on this page for every metric.
On the Kava RPC endpoints benchmark, PublicNode leads at 65 ms versus thirdweb at 519 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.