XRPL EVM RPC endpoints: free public URLs by latency
HTTP round-trip latency for the Tendermint `status` method against every free, no-key public XRPL EVM Cosmos SDK endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Peersyst has the lowest median latency of the 3 free public XRPL EVM RPC endpoints measured, 109 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/xrplevm-rpc. 3 public endpoints, no key: cosmos-rpc.xrplevm.org, xrp-rpc.polkachu.com, rpc.xrpl.cumulo.org.es. Full URLs with their 24h median are listed below.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
XRPL EVM is a Cosmos SDK chain (xrplevm_1440000-1) that brings an EVM execution environment to the XRP ecosystem. This page measures its Cosmos consensus RPC, which is a different surface from its EVM JSON-RPC: every endpoint the registry lists answered the Tendermint `status` probe on 2026-10-07, operated by Peersyst (cosmos-rpc.xrplevm.org), Cumulo and Polkachu. All three listed in the registry answered, which is the exception rather than the rule in this part of the cluster.
Methodology
XRPL EVM: 3 free public RPC endpoints answering Tendermint status every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Peersyst leads at 109 ms; the chain-official endpoint measures 109 ms. We measure the round-trip latency of a single Tendermint `status` call against every no-key public XRPL EVM endpoint that sustains continuous probing, 3 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a XRPL EVM-scaled staleness gap (20 blocks at XRPL EVM's ~3 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the XRPL EVM-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public XRPL EVM RPC endpoints ranked by p50 latency (24h, 3 regions)
Public XRPL EVM RPC endpoints measured
The 3 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
Peersysthttps://cosmos-rpc.xrplevm.org109 ms100.0%
Polkachuhttps://xrp-rpc.polkachu.com114 ms98.5%
Cumulohttps://rpc.xrpl.cumulo.org.es122 ms100.0%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Frequently asked
Which XRPL EVM RPCs work without an API key?
3 endpoints are probed on this chain: Peersyst (cosmos-rpc.xrplevm.org), Cumulo (rpc.xrpl.cumulo.org.es), Polkachu (xrp-rpc.polkachu.com). Every listed endpoint was live-verified with a Tendermint status call returning a parsable response before inclusion.
How is XRPL EVM RPC latency measured here, technically?
One identical Tendermint status call every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Is this the EVM endpoint or the Cosmos endpoint?
The Cosmos consensus endpoint. XRPL EVM exposes both: a Tendermint RPC that answers `status` and an EVM JSON-RPC that answers `eth_getBlockByNumber`. They are separate services with separate hostnames and separate latency, so mixing them in one column would compare different work. This board is the consensus surface; it does not tell you how fast a contract call returns.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities