Somnia public RPC endpoints, tested
Every keyless Somnia (chain ID 5031) 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. 3 of 3 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://api.infra.mainnet.somnia.network | 19 ms | 0 blocks | 1,000 | archive (1M+) |
| https://somnia-rpc.publicnode.com | 35 ms | 1 blocks | 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/somnia (SwiftNodes, keyless: 2 req/s) | 1718 ms | 47 blocks | 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/somnia(SwiftNodes): first head after 37 ms
Test any endpoint yourself with the RPC tester. Our Somnia endpoint, limits and status: Somnia RPC, uptime history.