- XRPL experienced a glitch within the last 24 hours.
- David Schwartz said the recent glitch is not a serious issue.
- The XRPL network is open to users who want to fix the identified issue.
The XRP Ledger (XRPL) experienced a glitch within the last 24 hours, and Ripple CTO David Schwartz believes it is not a serious issue. Schwartz reassured users that the ledger’s performance over the past 24 hours was “solid,” noting that the glitch might be linked to the monitoring system.
The XRPL glitch is a minor issue
In his latest post on X, Schwartz stated that the XRPL is currently handling 11,000 requests per second from 173 peers. According to Schwartz, approximately 0.006 seconds of the average request goes into the reply going out. Although Schwartz wasn’t certain about the incident, he noted that the glitch lasted for a short period.
Related Article: Ripple CTO Explains How XRPL and ILP Will Facilitate Seamless Payments
The Ripple CTO stated that the glitch lasted approximately one minute, during which the monitoring system failed to gather data for an unidentified reason. However, he told users that he is working on improvements to the collector, which he expects will fix the problem. Schwartz also believes that the glitch has nothing to do with the ledger’s hub.
The real issue and how to help resolve the problem
In the meantime, Schwartz clarified that the 11,000 requests he mentioned in his post included transactions, consensus validations, and servers querying for ledger data. Meanwhile, other requests comprise overhead for maintaining the network topology. He further explained to the network users that the “abuse” category registered on the page represents servers that were disconnected from the hub because it perceived them as placing excessive load on it.
Related Article: Ripple CTO: Why a Flood of New Blockchains Proves the XRPL’s Vision Was Right
Meanwhile, Schwartz provided further details on the issues experienced by the XRPL so that anyone interested could attempt to fix them. He noted that the glitch affected the peer link policing system, which he designed about eight years ago. According to Schwartz, the logic behind the solution is that they do not trust most of the peers on the network, considering some of them might be malicious.
The Ripple CTO encouraged interested solution providers to align with the outlined logic while trying to fix the problem and secure the network.
