X Layer public RPC endpoints, tested
Every keyless X Layer (chain ID 196) 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. 6 of 10 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.nodeflare.app/xlayer/public | 206 ms | 0 blocks | 1,000 | recent only |
| https://xlayer.drpc.org | 31 ms | 7 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/xlayer (SwiftNodes, keyless: 2 req/s) | 76 ms | 4 blocks | under 1,000 | archive (1M+) |
| https://xlayer-mainnet.rpc.sentio.xyz | 168 ms | 5 blocks | 10,000+ | archive (1M+) |
| https://rpc.xlayer.tech | 202 ms | 10 blocks | under 1,000 | archive (1M+) |
| https://xlayerrpc.okx.com | 250 ms | 9 blocks | under 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
xlayer.drpc.org: first head after 340 ms - does not stream
rpc.swiftnodes.io/ws/xlayer(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
endpoints.omniatech.io/v1/xlayer/mainnet/public: no answer (HTTP 521)rpc.ankr.com/xlayer: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403xlayer.rpc.blxrbdn.com: chainId: fetch failedlb.routeme.sh/rpc/evm/196: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our X Layer endpoint, limits and status: X Layer RPC, uptime history.