Umair
Key Takeaways
- The XRP Ledger resumed operations after a one-hour halt without any loss of user funds or data.
- Developers are conducting a post-mortem analysis to identify the halt’s root cause and prevent future incidents.
Share this article
The XRP Ledger has returned to normal operations after experiencing a one-hour network halt on February 4. Developers confirmed no loss of user funds during the incident.
The interruption, which stopped the creation of new ledgers at block 93,927,173, affected the network’s ability to process and record transactions, according to Ripple CTO David Schwartz.
The network is now recovering. We don’t know exactly what caused the issue yet.
Super-preliminary observation: It looked like consensus was running but validations were not being published, causing the network to drift apart. Validator operators manually intervened to choose a…
— David “JoelKatz” Schwartz (@JoelKatz) February 4, 2025
Although some network components, including consensus mechanisms, continued to function, the core process of adding new ledgers to the blockchain was temporarily suspended.
Network validators and developers collaborated to implement fix and restore functionality from the last confirmed ledger.
The precise nature of the technical issue that caused the halt is currently under investigation.
“The XRP Ledger has resumed forward progress,” said the XRPL developer team. “The @RippleXDev team is investigating the root cause and will provide updates as soon as possible.”
Schwartz suggested that the spontaneous recovery of the XRPL network was mainly due to its self-correcting nature.
“Very few UNL operators actually made any changes, as far as I can tell, so it’s possible the network spontaneously recovered. I’m not sure yet,” he stated.
The network’s built-in safeguards detected the halt and prevented potentially inconsistent ledgers from being trusted, maintaining asset security throughout the incident, Schwartz explained.
The incident follows a temporary network stall in late November last year, due to a bug that caused several nodes to crash. The issue resulted in a temporary halt to transaction processing for approximately 10 minutes.
Share this article
