Ronin public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://api-ronin-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c45 ms0 blocksunder 1,000recent only
https://ronin-mainnet.gateway.tatum.io25 ms8 blocksunder 1,000none
https://ronin.drpc.org29 ms33 blocksunder 1,000none
https://api.roninchain.com/rpc152 ms10 blocksunder 1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/ronin (SwiftNodes, keyless: 2 req/s)158 ms4 blocksunder 1,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

  • does not stream ronin.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
  • does not stream rpc.swiftnodes.io/ws/ronin (SwiftNodes): gateway: WebSocket not available for chain: ronin

Listed but not working

  • ronin.gateway.tenderly.co: chainId: rate limited
  • lb.routeme.sh/rpc/evm/2020: eth_blockNumber failed

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