XRPL Public Hubs Reach 423 Concurrent Connections, Abuse Metrics Near Zero

Reaching a peak of 423 concurrent connections, the number of public hubs on XRP Ledger (XRPL) has stabilized after the manifest flood incident. The abuse metric, which tracks malicious traffic, remains nearly at zero. David Schwartz, Ripple's former Chief Technology Officer, shared data collected between August 25 and September 8 showing an average of around 400 concurrent connections with a maximum of 423.
This indicator reflects the network infrastructure status following the manifest flood that occurred on July 31 around Korean time. The incident involved a large volume of manifest messages spreading across peer-to-peer networks, causing disconnections for multiple nodes while maintaining ledger consensus and transaction processing. No funds were lost, private keys exposed, or ledger integrity compromised.
The core issue was resource exhaustion at the peer layer rather than consensus failure. The official report suggested possible causes including outdated node versions, lingering manifest caches, or involvement of the updated 'xrpld' version. The cause and actor remain unspecified, with no confirmation on whether it was intentional or accidental during testing.
Ripple's development team released 'xrpld 3.2.1' on July 31 to address memory and processing resource overuse during manifest propagation. Subsequent updates like 'xrpld 3.3.0' added further restrictions on stored manifests, message size limits per item, and cache capacity. The latest data shows these patches have stabilized hub connections with abuse metrics nearly at zero.
However, the report notes this single-hub metric should not be extrapolated to represent the entire XRPL network's complete normalization. Network stability requires verification that patches are properly maintained across all node environments moving forward.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: XRPL 사설 허브 동시연결 423개, 악용 지표 거의 0