Stable public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://stable.drpc.org162 ms0 blocksunder 1,000none
https://rpc.stable.xyz52 ms25 blocks1,000none
https://rpc.swiftnodes.io/rpc/stable (SwiftNodes, keyless: 2 req/s)84 ms7 blocksunder 1,000recent only
https://lb.routeme.sh/rpc/evm/988146 ms14 blocksunder 1,000none
https://stable-mainnet.rpc.sentio.xyz182 ms21 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 rpc.swiftnodes.io/ws/stable (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

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