Polygon zkEVM public RPC endpoints, tested

Every keyless Polygon zkEVM (chain ID 1101) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: 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. 4 of 11 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	eth_getLogs	State
https://polygon-zkevm.drpc.org	25 ms	under 1,000	archive (1M+)
https://zkevm-rpc.com	30 ms	10,000+	archive (1M+)
https://poly-zkevm.api.pocket.network	79 ms	10,000+	recent only
https://rpc.swiftnodes.io/rpc/polygon-zkevm (SwiftNodes, keyless: 2 req/s)	147 ms	10,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 polygon-zkevm.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
does not stream poly-zkevm.api.pocket.network: connection failed (connect)
does not stream rpc.swiftnodes.io/ws/polygon-zkevm (SwiftNodes): subscribe rejected: method is not available on free plan, please upgrade to paid plan

Listed but not working

rpc.polygon-zkevm.gateway.fm: no answer (HTTP 404)
public.1rpc.io/polygon/zkevm: chainId: You've reached the usage limit for your current plan. To continue with higher limits and un
polygon-zkevm-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
polygon-zkevm-public.nodies.app: no answer (HTTP 500)
endpoints.omniatech.io/v1/polygon-zkevm/mainnet/public: no answer (HTTP 521)
node.histori.xyz/polygon-zkevm-mainnet/8ry9f6t9dct1se2hlagxnd9n2a: chainId: fetch failed
lb.routeme.sh/rpc/evm/1101: eth_blockNumber failed

Test any endpoint yourself with the RPC tester. Our Polygon zkEVM endpoint, limits and status: Polygon zkEVM RPC, uptime history.