RPCsUpdated

XRP Ledger RPC endpoints: free public URLs by latency

HTTP round-trip latency for ledger_current against every free, no-key public XRP Ledger node, audited every 60 seconds from 3 regions.

TL;DR. As of , Ripple is the only one of the 2 free public XRP Ledger RPC endpoints measured above the 50 % success floor, at 596 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/xrp-rpc. 2 public endpoints, no key: s1.ripple.com:51234, xrplcluster.com. 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 →

The XRP Ledger is a decentralized payment network using a federated consensus protocol (RPCA) that closes a new ledger every 3 to 4 seconds with instant, deterministic finality. Free public JSON-RPC endpoints are available without an API key from Ripple and XRPL Labs. Every provider was live-verified with consecutive keyless ledger_current probes at launch.

Methodology

XRP Ledger: 2 free public RPC endpoints answering `ledger_current` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Ripple leads at 596 ms. We measure the round-trip latency of a single JSON-RPC call (ledger_current) against every no-key public XRP Ledger node that sustains continuous probing: 2 providers live today, 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-scaled staleness gap (75 ledgers, around 5 min). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the XRP-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: {"method":"ledger_current","params":[{}]}. Plain HTTP POST. XRPL uses its own JSON-RPC envelope (no jsonrpc:2.0 field); errors are signalled via result.status='error'. 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 archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the XRP Ledger-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain=xrp. Provider coverage today: 2 no-key endpoints.

Results: 2 free public XRP Ledger RPC endpoints measured, 1 ranked by p50 latency (24h, 3 regions)

XRP Ledger RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1RippleRipple-operated public XRP Ledger mainnet node (s1), no key required596 ms636 ms700 ms100.00% (n=4321)
Measured, not ranked: sample below the ranking floor
not rankedXRPL LabsXRPL Labs cluster (xrplcluster.com), community-operated XRPL Foundation nodes, no key required207 ms296 ms1.30 s13.50% (n=4320)

Public XRP Ledger RPC endpoints measured

The 2 no-key endpoints answering our probes today, with their current 24h median; 1 of them sits below the 50 % success floor and is listed last. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.

  • Ripple logoRipplehttps://s1.ripple.com:51234596 ms100.0%
  • XRPL Labs logoXRPL Labshttps://xrplcluster.com207 ms13.5% ▾

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 XRP Ledger nodes work without an API key?

2 endpoints are probed on this chain, each listed with its URL, 24h median and success rate in the endpoints table on this page. Every listed endpoint was live-verified with a ledger_current POST returning a parsable ledger index before inclusion.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities