Rootstock public RPC endpoints, tested

Every keyless Rootstock (chain ID 30) 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. 4 of 7 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rootstock.drpc.org28 ms0 blocksunder 1,000archive (1M+)
https://public-node.rsk.co177 ms0 blocksunder 1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/rootstock (SwiftNodes, keyless: 2 req/s)185 ms0 blocksunder 1,000archive (1M+)
https://mycrypto.rsk.co194 ms0 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 rootstock.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan
  • does not stream rpc.swiftnodes.io/ws/rootstock (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • rootstock-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
  • rsk-mainnet.gateway.tatum.io: chainId: rate limited
  • lb.routeme.sh/rpc/evm/30: eth_blockNumber failed

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