The XRP Ledger (XRPL), one of the longest-running blockchain networks, experienced a rare disruption on Tuesday, February 5, 2025, when block production stalled at ledger height 93,927,173 for approximately one hour before spontaneously recovering. No assets or transactions were lost during the incident.
Cause: Consensus Drift Due to Unpublished Validations
Ripple CTO David Schwartz provided initial analysis in a post on X, explaining that the issue stemmed from the network failing to publish validations. “It looked like consensus was running but validations were not being published, causing the network to drift apart,” he wrote. Validator operators manually intervened to choose a sane starting point after the last ledger that anyone could have seen as fully validated and began publishing validations from there. Schwartz reassured the community that no funds were at risk, as servers recognized the issue and did not process untrusted ledgers.
Community Concerns and Reassurances
The halt raised immediate concerns about network security and transaction safety. However, Schwartz’s timely clarification helped calm users, emphasizing that even pending transactions remained intact. The incident demonstrated XRPL’s self-healing capability but also highlighted the need for ongoing improvements in validator coordination and network stability.
Historical Context and Decentralization Debate
This disruption follows a node crash in November 2024. The XRPL Foundation had previously expanded its Unique Node List (UNL) to enhance decentralization, but some critics argue that these changes may have contributed to network instability. While the direct link between the UNL expansion and this halt remains unconfirmed, it has fueled discussions about governance and trade-offs in decentralized networks.
Market Impact and Future Steps
Although XRP price experienced short-term volatility following the news, the swift recovery and absence of material losses stabilized market sentiment. Ripple’s team stated they will conduct a thorough root-cause analysis and optimize validator communication protocols to reduce recurrence. For long-term XRPL supporters, this self-recovery event reinforces confidence in the network’s resilience.

