Celo public RPC endpoints, tested
Every keyless Celo (chain ID 42220) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-08: 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. 6 of 11 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://celo.drpc.org | 62 ms | 2 blocks | under 1,000 | archive (1M+) |
| https://celo-mainnet.gateway.tatum.io | 84 ms | 0 blocks | under 1,000 | none |
| https://rpc.ankr.com/celo | 106 ms | 0 blocks | 1,000 | archive (1M+) |
| https://forno.celo.org | 61 ms | 5 blocks | 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/celo (SwiftNodes, keyless: 2 req/s) | 101 ms | 4 blocks | under 1,000 | recent only |
| https://rpc.celocolombia.org | 106 ms | – blocks | under 1,000 | none |
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
forno.celo.org/ws: first head after 524 ms - does not stream
celo.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan - does not stream
rpc.swiftnodes.io/ws/celo(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
celo-rpc.blockreq.com/v1/rpc/public: no answer (HTTP 410)celo-json-rpc.stakely.io: chainId: timeoutapi-celo-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limitedlb.routeme.sh/rpc/evm/42220: eth_blockNumber failedcelo.api.onfinality.io/public: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Celo endpoint, limits and status: Celo RPC, uptime history.