Celo public RPC endpoints, tested

Every keyless Celo (chain ID 42220) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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. 8 of 10 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://api-celo-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c42 ms0 blocksunder 1,000recent only
https://celo.drpc.org19 ms23 blocksunder 1,000archive (1M+)
https://forno.celo.org24 ms27 blocks1,000archive (1M+)
https://celo-json-rpc.stakely.io28 ms18 blocks10,000+recent only
https://celo-mainnet.gateway.tatum.io34 ms23 blocksunder 1,000none
https://rpc.celocolombia.org99 ms– blocksunder 1,000none
https://rpc.ankr.com/celo99 ms22 blocks1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/celo (SwiftNodes, keyless: 2 req/s)121 ms8 blocks1,000archive (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 forno.celo.org/ws: first head after 649 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

  • lb.routeme.sh/rpc/evm/42220: chainId: rate limited
  • celo.api.onfinality.io/public: chainId: rate limited

Test any endpoint yourself with the RPC tester. Our Celo endpoint, limits and status: Celo RPC, uptime history.