Immutable vs thirdweb

Immutable leads on the only live benchmark. Immutable wins on Fastest free Immutable zkEVM RPC, live no-key EVM endpoint latency (229 ms vs 674 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.

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

Immutable vs thirdweb: which one is better?

Immutable and thirdweb 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 thirdweb?

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

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

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.