PublicNode vs Tenderly

Side by side OpenChainBench measurements. Identical layout, no editorial verdict, the live data leads. Each panel surfaces the aggregate plus the chain and region breakdowns when the underlying bench exposes them, straight from the Prometheus queries that drive the parent benchmark pages.

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

Tenderly logo
Tenderly

Tenderly's public gateway exposes a no-key JSON-RPC endpoint per chain at `gateway.tenderly.co/public/<slug>`. Covers Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche, Linea, Scroll and Mantle. The same Tenderly platform behind the keyed Web3 dev suite.

Side by side measurements

Fastest free public RPC for Ethereum, BNB, Polygon and 7 more EVM chains

RPCs

PublicNode

Leads

39 ms

p99
86 ms
rank
#4
samples
86,396

Tenderly

Trails

121 ms

p99
777 ms
rank
#8
samples
77,758

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumPublicNode9 ms21 ms79 ms36 ms
Tenderly8 ms15 ms235 ms86 ms
PolygonPublicNode12 ms18 ms80 ms37 ms
Tenderly103 ms22 ms331 ms152 ms
ArbitrumPublicNode9 ms22 ms79 ms37 ms
Tenderly9 ms17 ms237 ms88 ms
OptimismPublicNode12 ms19 ms75 ms35 ms
Tenderly9 ms18 ms237 ms88 ms
BasePublicNode12 ms19 ms80 ms37 ms
Tenderly9 ms18 ms238 ms88 ms
AvalanchePublicNode9 ms20 ms76 ms35 ms
Tenderly99 ms18 ms327 ms148 ms
LineaPublicNode10 ms18 ms76 ms35 ms
Tenderly97 ms16 ms325 ms146 ms
ScrollPublicNode11 ms17 ms77 ms35 ms
Tenderly97 ms16 ms325 ms146 ms
MantlePublicNode11 ms18 ms79 ms36 ms
Tenderly98 ms18 ms326 ms147 ms

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.