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 , Cumulo has the lowest median latency of the 4 free public XRPL EVM RPC endpoints measured, 91 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/xrplevm-rpc. 4 public endpoints, no key: rpc.xrpl.cumulo.org.es, cosmos-rpc.xrplevm.org, xrp-rpc.polkachu.com, xrplevm-mainnet-rpc.itrocket.net. 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: 4 free public RPC endpoints answering Tendermint status every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Cumulo leads at 91 ms; the chain-official endpoint measures 110 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, 4 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.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
- Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"status","params":[]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the exclusion rules follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the XRPL EVM-scoped view of the same harness.
- Roster: every endpoint here answered a real Tendermint status call without a key on the 2026-10-07 sweep before being added to the probe matrix. An endpoint that needs a key, region-blocks us or rate-limits below the 60-second cadence is excluded rather than listed with an asterisk.
- Chain scope: every query on this page is pinned to `chain="xrplevm"`. Provider coverage: 4 no-key endpoints.
Results: 4 free public XRPL EVM RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | CumuloCumulo public Tendermint RPC endpoint for XRPL EVM | 91 ms | 120 ms | 501 ms | 99.95% (n=4322) |
| 2 | PeersystPeersyst official public Tendermint RPC endpoint for XRPL EVM | 110 ms | 156 ms | 629 ms | 100.00% (n=4314) |
| 3 | PolkachuPolkachu public Tendermint RPC endpoint for XRPL EVM | 111 ms | 122 ms | 200 ms | 100.00% (n=4322) |
| 4 | ITRocketITRocket validator public Tendermint RPC, listed on XRPL EVM's Public APIs page | 136 ms | 149 ms | 197 ms | 100.00% (n=4316) |
Public XRPL EVM RPC endpoints measured
The 4 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.
Cumulohttps://rpc.xrpl.cumulo.org.es91 ms100.0%Peersyst
https://cosmos-rpc.xrplevm.org110 ms100.0%Polkachu
https://xrp-rpc.polkachu.com111 ms100.0%ITRocket
https://xrplevm-mainnet-rpc.itrocket.net136 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?
4 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