XRP Ledger RPC throughput claims face scrutiny as verified benchmarks tell a different story

A claim circulating on social media that XRP Ledger RPC nodes can process 30,000 messages per second sounds impressive. The problem is that verified benchmarks don’t actually support that number. What the actual numbers show XRPL Labs, one of the primary infrastructure developers for the XRP Ledger, has been focused on latency rather than raw message throughput. Their public endpoint currently posts a p50 latency of approximately 371 milliseconds for ledger_current calls, making it the lowest-latency option among public XRPL servers. Public server clusters have been observed handling over 10,000 reads per second during peak usage periods. That’s a solid number for blockchain infrastructure, but it’s a third of the claimed 30,000 figure. GetBlock, another infrastructure provider, claims its XRPL nodes can process upward of 1,000 requests per second without rate limitations on dedicated setups. The closest anyone has gotten to the headline figure involves validator messaging, which is a fundamentally different category of traffic. Validator message handling has recorded averages around 3,260 messages per second under optimal testing conditions, with peaks above 6,100 messages per sec...