David Schwartz, Ripple CTO Emeritus and XRP Ledger chief architect, said his private XRPL relay hub has fully recovered from the July 2026 manifest-flood attack. The incident targeted the network’s peer-to-peer communication layer by sending large volumes of fake or unverified validator manifests, degrading connectivity without stopping ledger finalization or causing a fork. Telemetry from Aug. 25 through Sept. 8 showed 406 current peer connections versus a 401.12 average, with 135 inbound and 271 outbound peers. Median latency was 167.80 milliseconds against a 165.69-millisecond average, while the 90th percentile was 310.67 milliseconds and peaked at 1.49 seconds. Current disconnections were 73 per five minutes, below the 84.6 average, and abuse-related disconnects were about 0.67 per five minutes. Schwartz also said two blank monitoring-chart sections reflected monitoring-system problems rather than hub failures. Emergency releases, including xrpld 3.3.0-rc6 and the 3.2.1 hotfix released July 31, restricted untrusted manifest processing. The metrics cover one infrastructure view and do not establish that XRPL is immune to future disruptions.