Cronos public RPC endpoints, tested
Every keyless Cronos (chain ID 25) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: 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. 9 of 17 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://api-cronos-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c | 166 ms | 0 blocks | under 1,000 | none |
| https://cronos.drpc.org | 27 ms | 66 blocks | under 1,000 | archive (1M+) |
| https://cronos-evm-rpc.publicnode.com | 30 ms | 70 blocks | 10,000+ | none |
| https://cronos-rpc.blockreq.com/v1/rpc/public | 38 ms | 66 blocks | 1,000 | recent only |
| https://rpc.swiftnodes.io/rpc/cronos (SwiftNodes, keyless: 2 req/s) | 42 ms | 8 blocks | 10,000+ | none |
| https://evm.cronos.org | 48 ms | 75 blocks | 1,000 | archive (1M+) |
| https://lb.routeme.sh/rpc/evm/25 | 49 ms | 26 blocks | under 1,000 | none |
| https://rpc.vvs.finance | 65 ms | 57 blocks | 1,000 | archive (1M+) |
| https://cronos.rpc.sentio.xyz | 166 ms | 20 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
cronos-evm-rpc.publicnode.com: first head after 188 ms - streams
cronos.drpc.org: first head after 394 ms - does not stream
rpc.swiftnodes.io/ws/cronos(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc.nodeflare.app/cronos/public: chainId: unknown_chaincronos-rpc.elk.finance: chainId: fetch failedmmf-rpc.xstaking.sg: chainId: fetch failedpublic.1rpc.io/cro: chainId: timeoutendpoints.omniatech.io/v1/cronos/mainnet/public: no answer (HTTP 521)rpc.owlracle.info/cro/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)rpc.nebkas.ro: chainId: timeoutcro-mainnet.gateway.tatum.io: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Cronos endpoint, limits and status: Cronos RPC, uptime history.