0G public RPC endpoints, tested

Every keyless 0G (chain ID 16661) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: 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. 2 of 2 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://evmrpc.0g.ai22 ms0 blocks10,000+archive (1M+)
https://rpc.swiftnodes.io/rpc/0g (SwiftNodes, keyless: 2 req/s)109 ms3 blocks10,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

  • does not stream rpc.swiftnodes.io/ws/0g (SwiftNodes): timeout (subscribe)

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