XRP Ledger Down for 10 Minutes: Ripple Reacts Quickly

XRPL network stability enhanced through Rippled 2.3.0 update after node disruptions.
Caching layer bug identified as cause of missing ledger and network transaction halt.
RippleX to release a detailed root cause analysis after December 12 to mitigate risks.

The XRP Ledger (XRPL) went down briefly on November 25, 2024. This stopped transaction processing for about 10 minutes. RippleX has since urged validators and node operators to upgrade their networks to the latest version, Rippled 2.3.0. This will make the network more stable and prevent similar problems.

The network issue happened at around 13:39 UTC. Several XRPL nodes crashed and restarted, including Full History, Current Ledger, Pathfinding, and Submission nodes.

What Caused the Disruption?

During the instability, XRPL’s consensus mechanism focused on safety over progress, which delayed transaction processing. The network started working normally again at 13:49 UTC. No funds were lost, but new transactions were paused.

The issue came from a missing ledger segment, which stopped Ripple’s network and Full History servers. This stopped servers from seeing the current ledger, so they could not validate transactions.

Rippled 2.3.0 Update Prevents More Issues

In response to the issue, RippleX’s Vice President of Engineering, Brad Chase, said Rippled 2.3.0 is being rolled out. He said everyone needs to start using it right away. The problem came from a caching-layer bug that was added over six months ago during a code refactor.

The bug made inconsistent result types appear in certain conditions, which made servers crash. The issue was not found in initial testing, and there is no evidence of prior exploitation.

Brad Chase told XRPL node operators and validators to upgrade their systems to the 2.3.0 rippled release as soon as possible. He also thanked those who helped fix the issue.

However, RippleX said it will share detailed technical details about the root cause on December 12, after most servers have the patch. This will lower potential risks for unpatched nodes. The specific details of the bug are not being shared to ensure network safety.

Disclaimer: The information presented in this article is for informational and educational purposes only. The article does not constitute financial advice or advice of any kind. Coin Edition is not responsible for any losses incurred as a result of the utilization of content, products, or services mentioned. Readers are advised to exercise caution before taking any action related to the company.