Rootstock public RPC endpoints, tested
Every keyless Rootstock (chain ID 30) 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. 5 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rootstock.drpc.org | 33 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://mycrypto.rsk.co | 179 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://public-node.rsk.co | 184 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://lb.routeme.sh/rpc/evm/30 | 190 ms | 0 blocks | under 1,000 | none |
| https://rpc.swiftnodes.io/rpc/rootstock (SwiftNodes, keyless: 2 req/s) | 558 ms | 0 blocks | under 1,000 | archive (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
rpc.swiftnodes.io/ws/rootstock(SwiftNodes): first head after 100 ms - does not stream
rootstock.drpc.org: subscribed, no head in 15 s
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 instersk-mainnet.gateway.tatum.io: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Rootstock endpoint, limits and status: Rootstock RPC, uptime history.