The XRP Ledger released rippled version 2.2.1 on July 30, 2024, delivering a targeted fix for a critical server bug introduced in version 2.2.0. The issue affected the handling of certain RPC requests in rippled, the reference server implementation used by XRPL infrastructure operators, rather than representing a failure of the ledger’s underlying consensus mechanism.
XRPL urged operators already running 2.2.0 to install the corrective release as soon as possible, while servers on older versions were instructed to upgrade by August 14, 2024. Version 2.2.1 introduced no new protocol amendments, making the release primarily an operational reliability patch rather than a network-feature upgrade. The official XRPL release announcement remains the primary technical record of the update.
Critical Fix Targeted the Server’s RPC Layer
Remote Procedure Call interfaces allow wallets, exchanges and applications to query XRPL nodes and submit requests to the network. A defect at that layer can therefore disrupt infrastructure even when consensus and ledger validation continue functioning normally. The 2.2.1 release addressed server-side request handling without changing XRPL’s transaction rules or introducing a new ledger amendment.
The distinction is important for assessing the incident. XRPL’s official material describes the problem as a critical bug introduced in 2.2.0, but does not document a July 30 network-wide consensus failure or a separate post-mortem for a mainnet outage. The available evidence supports characterizing the event as a software regression requiring an urgent node upgrade, not as a breakdown of XRP Ledger consensus.
The XRP Ledger Foundation’s public rippled repository provides an independently inspectable technical history of server releases and subsequent changes. That release record also shows how rippled maintenance continues separately from amendments that modify consensus-level protocol behavior.
Testnet Reset Was a Separate August 2024 Event
XRPL also reset its Testnet on August 19, 2024, but that operation should not be treated as remediation for the RPC bug. The official Testnet notice said the reset was intended to improve stability and reduce node-operating costs while replenishing the finite supply of test XRP distributed through the faucet. The Testnet reset was therefore a separate infrastructure-maintenance event rather than part of the 2.2.1 security fix.
The dates are also historical rather than upcoming: both the July 30, 2024 rippled release and the August 19, 2024 Testnet reset occurred more than two years ago. For operators assessing XRPL infrastructure today, version 2.2.1 is best understood as an important 2024 maintenance milestone, not a current software release or pending network action. The current rippled release line has since advanced well beyond 2.2.1.
