Immutable zkEVM public RPC endpoints, tested
Every keyless Immutable zkEVM (chain ID 13371) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: does it answer on the right chain, how fast, how far behind the best head, how large an eth_getLogs range it accepts, whether it keeps archive state, and whether its WebSocket actually streams. 2 of 5 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.immutable.com | 117 ms | 0 blocks | 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/immutable-zkevm (SwiftNodes, keyless: 2 req/s) | 137 ms | 3 blocks | 1,000 | archive (1M+) |
Order: endpoints within 3 blocks of the best head first, then by median latency. Latency is measured from one server, so yours will differ by region; lag and limits do not.
WebSocket endpoints
- does not stream
immutable-zkevm.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan - does not stream
rpc.swiftnodes.io/ws/immutable-zkevm(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
immutable-zkevm.drpc.org: eth_blockNumber failedimmutable.gateway.tenderly.co: chainId: rate limitedlb.routeme.sh/rpc/evm/13371: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Immutable zkEVM endpoint, limits and status: Immutable zkEVM RPC, uptime history.