Cronos zkEVM RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Cronos zkEVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Cronos (Crypto.com) has the lowest median latency of the 2 free public Cronos zkEVM RPC endpoints measured, 159 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/cronos-zkevm-rpc. 2 public endpoints, no key: mainnet.zkevm.cronos.org, cronos-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 →
Cronos zkEVM (chain 388) is Crypto.com's zkEVM Layer 2 built on the zkSync Era stack, distinct from Cronos EVM. CRO is the bridged gas token. 2 keyless endpoints are probed continuously: the Cronos official mainnet gateway (mainnet.zkevm.cronos.org) and dRPC (cronos-zkevm.drpc.org).
Methodology
Cronos zkEVM: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Cronos (Crypto.com) leads at 159 ms; the chain-official endpoint measures 159 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Cronos zkEVM endpoint that sustains continuous probing, 2 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Cronos zkEVM-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.
- 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 Cronos zkEVM-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="cronos-zkevm"`. Provider coverage today: 2 no-key endpoints.
Results: 2 free public Cronos zkEVM RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Cronos (Crypto.com)Crypto.com official Cronos zkEVM public RPC | 159 ms | 178 ms | 412 ms | 100.00% (n=4321) |
| 2 | dRPCdRPC public gateway for Cronos zkEVM | 270 ms | 429 ms | 554 ms | 98.59% (n=4316) |
Public Cronos zkEVM RPC endpoints measured
The 2 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.
Cronos (Crypto.com)https://mainnet.zkevm.cronos.org159 ms100.0%
dRPChttps://cronos-zkevm.drpc.org270 ms98.6%
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 Cronos zkEVM RPCs work without an API key?
2 endpoints are probed on this chain, each listed with its URL in the endpoints table above.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities