zkSync Era public RPC endpoints, tested
Every keyless zkSync Era (chain ID 324) 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. 8 of 16 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://zksync.drpc.org | 26 ms | 2 blocks | under 1,000 | recent only |
| https://zksync-mainnet.gateway.tatum.io | 28 ms | 0 blocks | under 1,000 | none |
| https://zksync-era.api.pocket.network | 91 ms | 1 blocks | under 1,000 | recent only |
| https://mainnet.era.zksync.io | 124 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://api.zan.top/zksync-mainnet | 168 ms | 2 blocks | under 1,000 | recent only |
| https://zksync-era.rpc.sentio.xyz | 184 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://zksync.api.onfinality.io/public | 242 ms | 2 blocks | under 1,000 | recent only |
| https://rpc.swiftnodes.io/rpc/zksync (SwiftNodes, keyless: 2 req/s) | 394 ms | 0 blocks | 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
- streams
zksync-era.api.pocket.network: first head after 9789 ms - streams
zksync.drpc.org: first head after 10068 ms - streams
rpc.swiftnodes.io/ws/zksync(SwiftNodes): first head after 17315 ms
Listed but not working
go.getblock.io/f76c09905def4618a34946bf71851542: no answer (HTTP 401)zksync.meowrpc.com: chainId: fetch failedendpoints.omniatech.io/v1/zksync-era/mainnet/public: no answer (HTTP 521)public.1rpc.io/zksync2-era: chainId: You've reached the usage limit for your current plan. To continue with higher limits and unrpc.ankr.com/zksync_era: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403li-fi-redirect.intustechno.workers.dev/rpc: chainId: rate limitedapi-zksync-era-mainnet-full.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limitedlb.routeme.sh/rpc/evm/324: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our zkSync Era endpoint, limits and status: zkSync Era RPC, uptime history.