XRP Ledger Stability Returns After July Manifest Flood Attack

XRP Ledger remains stable two weeks after the July manifest flood attack, with 406 active connections and limited abuse-related disconnects.

The XRP Ledger has maintained stable network conditions for two weeks following a manifest flood attack in July that disrupted peer connectivity across the network, according to BSCNews.

David Schwartz, CTO Emeritus at Ripple and an architect of the XRP Ledger, reported that the XRP Ledger hub recorded 406 active connections during the monitoring period, compared with a recent average of 401. Median peer latency also remained close to its recent average, indicating that the network's peer-to-peer connectivity had remained broadly stable.

XRP Ledger Peer Connectivity Holds Steady

Schwartz's update provides several indicators of the network's condition following the July incident. In addition to the 406 active connections, peer disconnections have declined, while disconnects associated with abuse have remained limited.

The figures offer a comparison between the current network conditions and recent operating levels. The number of active connections is slightly above the recent average, while median peer latency has not shown a notable departure from its recent range.

BSCNews reported the update based on information shared by Schwartz, who has been closely associated with the technical architecture of the XRP Ledger.

July Attack Targeted Validator Manifests

The stability report follows a manifest flood attack that affected XRPL peer connectivity in July. According to BSCNews, attackers flooded nodes with fake or unverified validator manifests, placing additional CPU and memory pressure on affected systems.

Validator manifests are used within the network to provide information associated with validators. During the incident, the large volume of false or unverified manifests created additional resource demands on nodes.

As the pressure increased, nodes began disassociating from peers in an effort to prevent their available resources from being depleted. That behavior disrupted peer connectivity across portions of the XRP Ledger network.

Despite the disruption, the attack did not prevent the network from continuing to reach consensus. According to the information shared by BSCNews, sufficient validator connectivity remained available for consensus to continue during the incident.

Network Monitoring Shows Reduced Disconnections

The latest figures point to a different operating picture from the conditions observed during the July attack. Peer disconnections have declined, while abuse-related disconnects remain limited, according to Schwartz's monitoring update.

The reported 406 active connections also remain close to the recent average of 401. Median peer latency has similarly stayed near its recent average, providing another measure of network connectivity during the two-week monitoring period.

The update does not identify any new disruption or provide a broader assessment beyond the reported network metrics. Instead, it documents the current stability of the XRP Ledger following the connectivity problems caused by the July manifest flood.

For now, the key monitoring indicators cited by Schwartz are active peer connections, latency and disconnection levels, with the latest figures showing the XRP Ledger hub remaining stable for two weeks after the attack.

writer: Ethan Collins
Crypto Journalist
Ethan Collins reports on developments across the cryptocurrency and blockchain sector. His work covers market movements, protocol updates, regulatory changes, and emerging trends in digital assets.
He focuses on presenting complex topics in a clear and accessible manner for a broad readership.