Superseed public RPC endpoints, tested
Every keyless Superseed (chain ID 5330) 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. 4 of 4 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.swiftnodes.io/rpc/superseed (SwiftNodes, keyless: 2 req/s) | 79 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://lb.routeme.sh/rpc/evm/5330 | 278 ms | 0 blocks | under 1,000 | none |
| https://superseed.drpc.org | 38 ms | 8 blocks | under 1,000 | archive (1M+) |
| https://mainnet.superseed.xyz | 161 ms | 5 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
- does not stream
mainnet.superseed.xyz: connection failed (connect) - does not stream
superseed.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan - does not stream
rpc.swiftnodes.io/ws/superseed(SwiftNodes): gateway: WebSocket not available for chain: superseed
Test any endpoint yourself with the RPC tester. Our Superseed endpoint, limits and status: Superseed RPC, uptime history.