Cronos RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Cronos RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Cronos has the lowest median latency of the 3 free public Cronos RPC endpoints measured, 56 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/cronos-rpc. Chain ID 25. 3 public endpoints, no key: evm.cronos.org, cronos-evm-rpc.publicnode.com, cronos.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 fields 3 no-key providers and encodes an integration trap from our sweep: PublicNode serves the chain at `cronos-evm-rpc.publicnode.com` (the intuitive `cronos-rpc` subdomain resolves but returns non-JSON). Tenderly's public gateway does not reach Cronos, making this one of the few pages in the Arbitrum after its keyless per-IP daily budget proved too tight for continuous multi-chain probing. Probes every 60 seconds from three regions with the cluster's anti-cache payload.
Methodology
Cronos: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Cronos leads at 56 ms; the chain-official endpoint measures 56 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Cronos 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 Cronos-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public Cronos RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Cronos | 56 ms | 74 ms | 145 ms | 100.00% |
| 2 | PublicNode | 72 ms | 85 ms | 226 ms | 99.77% |
| 3 | dRPC | 91 ms | 112 ms | 198 ms | 99.58% |
Public Cronos RPC endpoints measured
Chain ID 25, currency CRO. 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.
Cronoshttps://evm.cronos.org56 ms100.0%
PublicNodehttps://cronos-evm-rpc.publicnode.com72 ms99.8%
dRPChttps://cronos.drpc.org91 ms99.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 RPCs work without an API key?
3 endpoints are probed on this chain: PublicNode (at `cronos-evm-rpc.publicnode.com`, note the non-intuitive subdomain), dRPC, and the chain-linked public endpoint. Tenderly's public gateway does not reach Cronos, and 1RPC was descoped cluster-wide to Ethereum and Arbitrum because its keyless per-IP daily budget cannot sustain continuous multi-chain probing. Every listed endpoint was live-verified before inclusion.
Why isn't MeowRPC listed on Cronos?
We tried it. MeowRPC's long-tail endpoints no longer resolve (DNS gone), and the provider appears defunct outside a few legacy chains, so it failed the live verification, eth_chainId match plus sustained probing, that gates admission to this cluster. Directories still listing it are copying stale metadata; this bench only ranks endpoints that answer.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities