On the 5th, the XRP Ledger (XRPL) experienced a temporary halt in block generation. At block height 93,927,173, network activity was suspended for approximately one hour, causing a pause in transaction processing.
David Schwartz, CTO of U.S.-based Ripple, explained that while the consensus mechanism remained operational, the verification results were not properly published, leading to a network partition.
The exact cause of the disruption is still under investigation, but initial analysis suggests issues related to consensus. Specifically, it appears that validators did not function correctly, causing the network to "drift" and lose synchronization.
After approximately 64 minutes of downtime, the network automatically recovered. According to Schwartz, a small number of validator operators manually intervened by selecting a trusted starting point from the last fully validated ledger, allowing the verification process to resume. This intervention likely facilitated the network’s realignment and restoration of normal operations. However, it remains unclear whether manual intervention was the direct solution or if the network autonomously recovered.
No losses of assets or transactions have been reported due to this temporary halt, and user funds remain secure. However, the delay of approximately 88,000 transactions is a significant concern, raising questions about the network’s stability.
While the XRP Ledger has maintained robust performance historically, this incident has highlighted areas that require improvement for future operations. It has become evident that if validator verification results are not properly published, there is a risk of network downtime, emphasizing the need for enhanced stability measures.