XRP ledger full history cluster

High available, low latency & geographic routing. Provided by the XRPLF with support from trusted community members.

  • Filters out transactions sent to verified scam accounts using XRP Forensics
  • Filters out transactions with unnecessary high transaction fee (> 2 XRP)
  • Seamless node failover without having to reconnect the WebSocket
  • Automatic routing of submit transactions to a dedicated (lowest fee) XRPL node pool.

Connect to wss://
Just like many other clients 🚀

If you want to connect to the XRP ledger using websockets for transaction history or transaction submission, you can now use the publicly available wss:// endpoint. Based on latency you will be routed to the closest, best available full history XRPL node.

High performance

Low latency, high performance. Multiple global points of presence, multiple community provided full history servers.


Multiple networks, multiple proxies, multiple full history servers. With live migration in case of downtime or maintenance.

Provided by the XRPLF

The infrastructure required to offer this service is provided by the XRPLF and XRPL community members. Because we will all benefit when the ecosystem grows.

Close to you

New York NYC, San Francisco SFO, Singapore SGP, Toronto TOR, Bangalore BLR, London LON & Falkenstein FSN

Fair use policy applies! By default the cluster accepts up to 5 simultaneous connections per client and up 1000 messages per client per minute. These numbers are not guaranteed: based on load, availability and query resource cost limits may be adjusted on the fly. For power users & commercial use, please run/obtain your own node(s).
Please note: for quality purposes, client IP addresses transmitting messages to the XRP ledger using wss:// may be recorded.

Want to try it?

Connected 🎉
Sent a server_info request and got response in milliseconds

Connection error: unknown

For developers

Points of presence
Available ledgers
Full history nodes
Yearly traffic
Live stats publicly available at: