Sei public RPC endpoints, tested
Every keyless Sei (chain ID 1329) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-08: 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. 4 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://sei.api.pocket.network | 60 ms | 0 blocks | 1,000 | recent only |
| https://rpc.swiftnodes.io/rpc/sei (SwiftNodes, keyless: 2 req/s) | 9 ms | 12 blocks | under 1,000 | recent only |
| https://evm-rpc.sei-apis.com | 44 ms | 13 blocks | 1,000 | archive (1M+) |
| https://sei.drpc.org | 74 ms | 8 blocks | under 1,000 | recent only |
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
sei.api.pocket.network: first head after 175 ms - streams
evm-ws.sei-apis.com: first head after 284 ms - streams
sei.drpc.org: first head after 340 ms - does not stream
rpc.swiftnodes.io/ws/sei(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
sei-evm-rpc.stakeme.pro: no answer (HTTP 403)sei-public.nodies.app: no answer (HTTP 404)lb.routeme.sh/rpc/evm/1329: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Sei endpoint, limits and status: Sei RPC, uptime history.