XRPL EVM public RPC endpoints, tested

Every keyless XRPL EVM (chain ID 1440000) 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. 3 of 3 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://xrpl.drpc.org27 ms0 blocksunder 1,000archive (1M+)
https://rpc.xrplevm.org121 ms0 blocks10,000+archive (1M+)
https://rpc.swiftnodes.io/rpc/xrpl-evm (SwiftNodes, keyless: 2 req/s)137 ms1 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 xrpl.drpc.org: first head after 13 ms
  • streams ws.xrplevm.org: first head after 2446 ms
  • does not stream rpc.swiftnodes.io/ws/xrpl-evm (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

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