Stable public RPC endpoints, tested
Every keyless Stable (chain ID 988) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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. 3 of 5 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://stable-mainnet.rpc.sentio.xyz | 166 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.stable.xyz | 25 ms | 4 blocks | 1,000 | none |
| https://rpc.swiftnodes.io/rpc/stable (SwiftNodes, keyless: 2 req/s) | 59 ms | 7 blocks | 1,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/stable(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
stable.drpc.org: eth_blockNumber failedlb.routeme.sh/rpc/evm/988: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Stable endpoint, limits and status: Stable RPC, uptime history.