Orderly public RPC endpoints, tested
Every keyless Orderly (chain ID 291) 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. 2 of 4 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.swiftnodes.io/rpc/orderly (SwiftNodes, keyless: 2 req/s) | 201 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://rpc.orderly.network | 249 ms | 0 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
rpc.swiftnodes.io/ws/orderly(SwiftNodes): gateway: WebSocket not available for chain: orderly
Listed but not working
orderly.drpc.org: eth_blockNumber failedlb.routeme.sh/rpc/evm/291: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Orderly endpoint, limits and status: Orderly RPC, uptime history.