PublicNode vs Thirdweb

PublicNode leads on 3 of 3 shared benchmarks, Thirdweb on 0. PublicNode wins on Fastest free Kava RPC, live no-key EVM endpoint latency (121 ms vs 609 ms), Fastest free Metis RPC, live no-key EVM endpoint latency (204 ms vs 610 ms), Fastest free Arbitrum Nova RPC, live no-key EVM endpoint latency (146 ms vs 610 ms).

Read methodology Last measured Window: rolling 24h3 shared benchmarks
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.

Thirdweb logo
Thirdweb

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).

Side by side measurements

Frequently asked questions

PublicNode vs Thirdweb: which one is better?

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.

Which is faster on fastest free kava rpc, live no-key evm endpoint latency, PublicNode or Thirdweb?

On the Fastest free Kava RPC, live no-key EVM endpoint latency benchmark, PublicNode leads at 121 ms versus Thirdweb at 609 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the PublicNode vs Thirdweb 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

A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.

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