Immutable vs Tenderly Gateway

Immutable leads on the only live benchmark. Immutable wins on Fastest free Immutable zkEVM RPC, live no-key EVM endpoint latency (228 ms vs 326 ms).

Read methodology Last measured Window: rolling 24h1 shared benchmark
Immutable logo
Immutable

Immutable's official public zkEVM RPC (rpc.immutable.com) for the Polygon CDK zkEVM L2 dedicated to Web3 gaming (chain 13371). Standard EVM JSON-RPC, keyless, rate-limited per IP.

Tenderly Gateway logo
Tenderly Gateway

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

Frequently asked questions

Immutable vs Tenderly Gateway: which one is better?

Immutable and Tenderly Gateway are compared on 1 shared OpenChainBench benchmarks. Immutable leads on Fastest free Immutable zkEVM RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.

Which is faster, Immutable or Tenderly Gateway?

On the Fastest free Immutable zkEVM RPC, live no-key EVM endpoint latency benchmark, Immutable leads at 228 ms versus Tenderly Gateway at 326 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the Immutable vs Tenderly Gateway 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

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.

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