Shibarium public RPC endpoints, tested
Every keyless Shibarium (chain ID 109) 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. 3 of 4 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.shibarium.shib.io | 24 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://shibarium.drpc.org | 31 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/shibarium (SwiftNodes, keyless: 2 req/s) | 99 ms | 1 blocks | 10,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
shibarium.drpc.org: first head after 2639 ms - does not stream
rpc.swiftnodes.io/ws/shibarium(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
shib.nownodes.io: no answer (HTTP 422)
Test any endpoint yourself with the RPC tester. Our Shibarium endpoint, limits and status: Shibarium RPC, uptime history.