Celo RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Celo RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode has the lowest median latency of the 4 free public Celo RPC endpoints measured, 73 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/celo-rpc. Chain ID 42220. 4 public endpoints, no key: celo-rpc.publicnode.com, forno.celo.org, gateway.tenderly.co, celo.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 →
Celo brings 4 no-key providers anchored by Forno (`forno.celo.org`), cLabs' public endpoint that predates most of the gateway industry. Since Celo's migration to an Ethereum L2 the RPC surface is standard EVM, so the multi-chain gateways compete directly with the house endpoint on the identical `eth_getBlockByNumber` probe every 60 seconds from three regions.
Methodology
Celo: 4 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. PublicNode leads at 73 ms; the chain-official endpoint measures 110 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Celo endpoint that sustains continuous probing, 4 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 Celo-scoped answer with per-region breakdowns as a first-class dimension.
Results: 4 free public Celo RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | PublicNode | 73 ms | 83 ms | 257 ms | 100.00% |
| 2 | Celo (Forno) | 110 ms | 221 ms | 372 ms | 100.00% |
| 3 | Tenderly | 154 ms | 162 ms | 195 ms | 100.00% |
| 4 | dRPC | 252 ms | 519 ms | 989 ms | 53.25% |
Public Celo RPC endpoints measured
Chain ID 42220, currency CELO. The 4 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.
PublicNodehttps://celo-rpc.publicnode.com73 ms100.0%
Celo (Forno)https://forno.celo.org110 ms100.0%
Tenderlyhttps://gateway.tenderly.co/public/celo154 ms100.0%
dRPChttps://celo.drpc.org252 ms53.3%
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 Celo RPCs work without an API key?
The 4 providers on this page are listed with their URLs in the endpoints table above. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.
Is Forno still the right default RPC for Celo?
Forno is stable and honest, but it is a single origin, so at least two of our three probe regions always pay cross-ocean latency to reach it. The current leader above (PublicNode at 73 ms) reflects the 3-region average; if your traffic is single-region, open that region's tab, Forno's ranking moves markedly by origin.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities