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.
Read also: RippleX Overhauls XRPL Testnet, To Enhance Stability
The issue came from a missing ledger segment, which stopped Ripple’s network and Full History servers. This …
The post XRP Ledger Down for 10 Minutes: Ripple Reacts Quickly appeared first on Coin Edition.
Read More
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.
Read also: RippleX Overhauls XRPL Testnet, To Enhance Stability
The issue came from a missing ledger segment, which stopped Ripple’s network and Full History servers. This …
The post XRP Ledger Down for 10 Minutes: Ripple Reacts Quickly appeared first on Coin Edition.
Read More