Fastest free Canto RPC, live no-key endpoint latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Canto RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Canto Official leads rpc latency at 183 ms (p50, 24h) on Fastest free Canto RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/canto-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Canto is a permissionless EVM L1 (chain 7700) built around free public infrastructure; its DEX, lending market, and stablecoin are protocol primitives rather than third-party dApps. The official endpoint (`canto.gravitychain.io`) is maintained by Plex, with dRPC, PublicNode, and Ankr providing additional keyless alternatives probed every 60 seconds from three regions.
Methodology
Per-chain member of the RPC latency cluster, extended to Canto. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Canto endpoint that sustains continuous probing, 4 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) so the leaderboard rewards sustained availability rather than fast error messages. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Canto-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Canto RPC right now?
Canto Official currently leads at 183 ms (`eth_getBlockByNumber` p50 over the last 24h), measured against 4 no-key providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Canto RPCs work without an API key?
4 endpoints sustain continuous keyless probing at launch: Canto Official, dRPC, PublicNode, Ankr. Every listed endpoint was live-verified before inclusion.
Does the fastest Canto RPC change by region?
Often. The region tabs at the top of the page re-scope every number to a single origin; pick the one closest to where your requests originate.
How is Canto RPC latency measured here?
One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against each provider from each of 3 regions. Responses are classified so an endpoint stuck on an old head or returning errors is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities