Fastest free Immutable zkEVM RPC, live no-key EVM endpoint latency
Immutable leads rpc latency at 224 ms (p50, 24h) on Fastest free Immutable zkEVM RPC, live no-key EVM endpoint latency. HTTP round-trip latency for the `eth_getBlockByNumber(\"latest\", false)` method against every free, no-key public Immutable zkEVM EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Immutable leads rpc latency at 224 ms (p50, 24h) on Fastest free Immutable zkEVM RPC, live no-key EVM endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/immutable-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Immutable zkEVM is a Polygon CDK zkEVM L2 (chain 13371) operated by Immutable, dedicated to Web3 gaming with an IMX gas token model, 2 s block cadence, settlement onto Ethereum via zk-proofs. 4 clean keyless providers live-verified at launch: `immutable-official` (rpc.immutable.com), dRPC, Tenderly Gateway, Thirdweb. Excluded by the launch audit: PublicNode (no `immutable` subdomain), Alchemy public (chain not enabled on public tier), Tenderly's `rpc.immutable.gateway.tenderly.co` alias (route redirects to keyed path).
Methodology
Per-chain member of the RPC latency cluster, extended to Immutable zkEVM. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber(\"latest\", false)`) against every no-key public Immutable zkEVM endpoint that sustains continuous probing, 4 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Immutable zkEVM-scaled staleness gap (25 blocks at Immutable zkEVM's ~2 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Immutable zkEVM-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Immutable zkEVM RPC right now?
Immutable currently leads at 224 ms (`eth_getBlockByNumber("latest", false)` p50 over the last 24h), measured against 4 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples. Use the region tabs to see the leader from the origin closest to your deployment.
Which Immutable zkEVM RPCs work without an API key?
4 endpoints sustain continuous keyless probing at launch. Every listed endpoint was live-verified with a `eth_getBlockByNumber` POST returning a parsable response before inclusion. See the methodology section for the endpoints that were audited and excluded.
Does the fastest Immutable zkEVM RPC change by region?
Often. Public infra concentrates in specific regions; a gateway that wins from Amsterdam can lose from Singapore by multiples. The region tabs at the top of the page re-scope every number to a single origin; pick the one closest to where your requests originate.
How is Immutable zkEVM RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` POST every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities