The XRP Ledger released a hotfix, xrpld v3.2.1, on July 31, 2026, to stop a validator manifest flooding issue that was chewing through memory and bandwidth on affected nodes. The bug didn't halt consensus or slow transaction processing, but it did hammer node stability hard enough that the team pushed out an urgent patch.
What the bug did
Validator manifests are how the network identifies and manages validator keys, linking identities, signing keys, and operator info. In this case, a flood of those manifests caused some nodes to balloon in memory use and soak up bandwidth. It was a resource problem, not a network-integrity problem. Still, if left unchecked, it could have made nodes sluggish or even knocked them offline.
The outage wasn't a consensus failure. Transactions kept moving. But for node operators running infrastructure, the extra load was real trouble.
The fix and the double restart
The patch is straightforward: upgrade to xrpld v3.2.1. Operators are also told to perform a double restart as part of the fix. That's not a typo. The team wants the restart done twice, likely to make sure the fix fully clears any lingering state from the flooding.
If you run a node, you should get on it. The hotfix is out now, and there's no reason to sit on the old version.
Why stability matters
Operational stability is the boring but crucial part of blockchain adoption. Institutions, exchanges, and infrastructure providers need to trust that nodes won't randomly spike in resource use. A bug like this doesn't break the network, but it tests patience and could spook the people who care about uptime. The XRP Ledger team moved fast, which is the right call.
The hotfix is separate from the upcoming v3.3.0 release, which is expected to bring new amendments that require validator approval. That's a bigger deal, with governance implications. For now, the immediate job is getting everyone onto v3.2.1 and watching for any residual flooding. The next release will have its own timeline, but it won't wait on this patch.
