{"slug":"xrp-rpc","title":"XRP Ledger RPC endpoints: free public URLs by latency","subtitle":"HTTP round-trip latency for ledger_current against every free, no-key public XRP Ledger node, audited every 60 seconds from 3 regions.","category":"RPCs","metric":"RPC latency","unit":"ms","status":"live","higherIsBetter":false,"filters":null,"value":598.109,"leader":{"name":"Ripple","slug":"ripple","value":598.109},"leaders":[{"name":"Ripple","slug":"ripple","value":598.109}],"rankings":[{"name":"Ripple","slug":"ripple","value":598.109,"unit":"ms","ms":{"p50":598.109,"p90":637.248,"p99":706.543,"mean":601.899},"successRate":100,"sampleSize":4319.75}],"sparkline":[593.779,593.64,592.241,593.715,595.963,600.057,603.075,604.424,602.925,612.646,613.964,616.905,606.131,606.735,603.506,604.132,601.469,598.697,596.672,594.521,595.211,603.647,605.332,611.761,603.798,605.77,604.312,604.804,600.846,598.698,593.076,598.917,595.582,608.872,602.645,604.254,596.274,596.702,595.649,592.293,587.692,589.018,591.051,598.069,597.507,595.435,591.722,591.032,593.099,597.206,600.958,605.534,606.364,606.215,607.105,608.33,609.379,603.169,603.087,600.47,601.166,610.185,613.668,618.668,608.195,603.586,603.099,602.61,603.193,599.73,601.556,606.339,608.594],"sampleSize":8639.64,"asOf":"2026-11-22T10:01:47.615Z","freshness":{"asOf":"2026-11-22T10:01:47.615Z","ageHours":0.1,"stale":false},"measured":2,"ranked":1,"headline":"Ripple is the only one of the 2 free public XRP Ledger RPC endpoints measured above the 50 % success floor, at 598 ms (p50, 24h, 3 regions).","quote":"Ripple is the only one of the 2 free public XRP Ledger RPC endpoints measured above the 50 % success floor, at 598 ms (p50, 24h, 3 regions). Source: OpenChainBench (https://openchainbench.com/benchmarks/xrp-rpc).","cite":{"plain":"OpenChainBench. \"XRP Ledger RPC endpoints: free public URLs by latency\". Retrieved 2026-11-22. https://openchainbench.com/benchmarks/xrp-rpc","bibtex":"@misc{ocb_xrp_rpc,\n  author = {OpenChainBench},\n  title  = {XRP Ledger RPC endpoints: free public URLs by latency},\n  year   = {2026},\n  url    = {https://openchainbench.com/benchmarks/xrp-rpc},\n  note   = {Retrieved 2026-11-22}\n}","apa":"OpenChainBench. (2026). XRP Ledger RPC endpoints: free public URLs by latency. Retrieved November 22, 2026, from https://openchainbench.com/benchmarks/xrp-rpc","ris":"TY  - GEN\r\nAU  - OpenChainBench\r\nTI  - XRP Ledger RPC endpoints: free public URLs by latency\r\nPY  - 2026\r\nUR  - https://openchainbench.com/benchmarks/xrp-rpc\r\nY2  - 2026-11-22\r\nER  - \r\n"},"pageUrl":"https://openchainbench.com/benchmarks/xrp-rpc","ogImage":"https://openchainbench.com/api/og/xrp-rpc","source":"https://github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities","methodology":["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](https://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."],"license":"CC-BY-4.0"}