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-11-22: 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. 7 of 10 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://xlayer.drpc.org29 ms2 blocksunder 1,000archive (1M+)
https://xlayer-mainnet.rpc.sentio.xyz169 ms0 blocksunder 1,000archive (1M+)
https://rpc.nodeflare.app/xlayer/public175 ms1 blocksunder 1,000archive (1M+)
https://api.blockvectra.com/v1/xlayer_mainnet/public17 ms4 blocksunder 1,000recent only
https://rpc.swiftnodes.io/rpc/xlayer (SwiftNodes, keyless: 2 req/s)46 ms6 blocksunder 1,000archive (1M+)
https://xlayerrpc.okx.com194 ms4 blocksunder 1,000archive (1M+)
https://rpc.xlayer.tech221 ms4 blocksunder 1,000archive (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 21 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: 403
  • lb.routeme.sh/rpc/evm/196: eth_blockNumber failed

Test any endpoint yourself with the RPC tester. Our X Layer endpoint, limits and status: X Layer RPC, uptime history.