RPCsUpdated

zkSync Era RPC endpoints: free public URLs by latency

HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public zkSync Era RPC endpoint, audited every 60 seconds from 3 regions.

TL;DR. As of , zkSync has the lowest median latency of the 3 free public zkSync Era RPC endpoints measured, 129 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/zksync-rpc. Chain ID 324. 3 public endpoints, no key: mainnet.era.zksync.io, zksync.drpc.org, gateway.tenderly.co. 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 →

zkSync Era is the only chain in our entire probe matrix with no PublicNode endpoint: both plausible subdomains 404, a genuine rarity for a provider that covers 70+ chains. That leaves dRPC, Tenderly and Matter Labs' own `mainnet.era.zksync.io` answering the identical `eth_getBlockByNumber` probe every 60 seconds from three regions, with stale-head detection against the cross-provider tip.

Methodology

zkSync Era: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. zkSync leads at 129 ms; the chain-official endpoint measures 129 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public zkSync Era endpoint that sustains continuous probing, 3 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness also classifies every response (ok / http_err / jsonrpc_err / stale / timeout) and audits archive depth every 5 minutes, so the leaderboard rewards sustained, honest availability rather than a fast error message. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the zkSync Era-scoped answer with per-region breakdowns as a first-class dimension.

  • Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
  • Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the zkSync Era-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain="zksync". Provider coverage: 3 no-key public-read endpoints live today, each listed with its URL in the endpoints table on this page. Exclusions follow the cluster-wide rules documented on the parent benchmark.

Results: 3 free public zkSync Era RPC endpoints ranked by p50 latency (24h, 3 regions)

zkSync Era RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1zkSyncMatter Labs public RPC, zkSync Era only129 ms141 ms1.38 s99.98% (n=4316)
2dRPCDecentralized RPC mesh, consensus-checked148 ms175 ms615 ms99.03% (n=4320)
3TenderlyMulti-chain public gateway, no key156 ms163 ms193 ms100.00% (n=4321)

Public zkSync Era RPC endpoints measured

Chain ID 324, currency ETH. The 3 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.

  • zkSync logozkSynchttps://mainnet.era.zksync.io129 ms100.0%
  • dRPC logodRPChttps://zksync.drpc.org148 ms99.0%
  • Tenderly logoTenderlyhttps://gateway.tenderly.co/public/zksync156 ms100.0%

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.

Frequently asked

Which zkSync Era RPCs work without an API key?

3 endpoints are probed on this chain; each is listed with its URL, 24h median and success rate in the endpoints table on this page, and the list changes as providers come and go.

Why is PublicNode not listed for zkSync Era?

Because it does not serve the chain: both plausible PublicNode subdomains returned 404 in our 2026-07-03 verification sweep, making zkSync Era the only chain we probe without a PublicNode endpoint. The bench lists what actually answers, not what coverage pages claim, so the leaderboard has 3 providers and zkSync (129 ms) currently leads them.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities