Nodies 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
Nodies logo
Nodies

Nodies is the surviving public-RPC frontend for POKT Network's decentralized infrastructure. Per-chain subdomains like `eth-pokt.nodies.app`, `polygon-pokt.nodies.app`, `arb-pokt.nodies.app`. Covers most major EVM chains no-key.

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

Nodies

Leads

117 ms

p99
196 ms
rank
#7
samples
60,482

Tenderly

Trails

121 ms

p99
777 ms
rank
#8
samples
77,758

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumNodies110 ms20 ms178 ms103 ms
Tenderly8 ms15 ms235 ms86 ms
PolygonNodies110 ms20 ms180 ms103 ms
Tenderly103 ms22 ms331 ms152 ms
ArbitrumNodies115 ms21 ms179 ms105 ms
Tenderly9 ms17 ms237 ms88 ms
OptimismNodies116 ms21 ms182 ms106 ms
Tenderly9 ms18 ms237 ms88 ms
BaseNodies199 ms110 ms266 ms192 ms
Tenderly9 ms18 ms238 ms88 ms
AvalancheNodies116 ms23 ms184 ms108 ms
Tenderly99 ms18 ms327 ms148 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.