Immutable zkEVM RPC endpoints: free public URLs by 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 has the lowest median latency of the 2 free public Immutable zkEVM RPC endpoints measured above the 50 % success floor (3 listed), 125 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/immutable-rpc. Chain ID 13371. 3 public endpoints, no key: rpc.immutable.com, immutable.gateway.tenderly.co, immutable-zkevm.drpc.org. Full URLs with their 24h median are listed below.
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. 3 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
Immutable zkEVM: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Immutable leads at 125 ms; the chain-official endpoint measures 125 ms. 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, 3 providers live today, 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.
Results: 3 free public Immutable zkEVM RPC endpoints measured, 2 ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Immutable | 125 ms | 129 ms | 160 ms | 100.00% (n=4331) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | Tenderly Gateway | 139 ms | 149 ms | 159 ms | 100.00% (n=4310) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Measured, not ranked: sample below the ranking floor | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| not ranked | dRPC | 262 ms | 451 ms | 825 ms | 37.70% (n=4330) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Public Immutable zkEVM RPC endpoints measured
Chain ID 13371, currency IMX. The 3 no-key endpoints answering our probes today, with their current 24h median; 1 of them sits below the 50 % success floor and is listed last. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
Immutablehttps://rpc.immutable.com125 ms100.0%
Tenderly Gatewayhttps://immutable.gateway.tenderly.co139 ms100.0%
dRPChttps://immutable-zkevm.drpc.org262 ms37.7% ▾
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://immutable-zkevm.rpc.thirdweb.com1.4 % success over 24 h
Frequently asked
Which Immutable zkEVM RPCs work without an API key?
4 endpoints are probed on this chain. 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.
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