XRP Ledger Operations announced that the Testnet and Devnet networks will be reset on November 25 between 5 p.m. and 6 p.m. Pacific Time, according to BeInCrypto. The maintenance is necessary because a server storing the complete transaction history for Testnet crashed, and Ripple stated that the system cannot recover without a full reset.
Infrastructure Failure and Recovery
The reset will permanently erase all on-chain state on the affected networks, including accounts, tokens, automated market makers (AMMs), transaction records, balances, and trading setups. Developers using these practice environments to test new payment systems and blockchain features without risking real money will need to re-fund and re-setup their testing environments after the maintenance window.
Ripple is increasing storage capacity to prevent similar problems in the future. This is not the first time the company has performed such maintenance; Ripple successfully reset the Devnet in October 2025. The official announcement confirmed that the resets affect Testnet and Devnet only, while other networks, including Mainnet, will continue to operate as usual.
Mainnet Operations Continue
Real XRP holdings and transactions will remain unaffected by the reset. XRP holders can continue sending, receiving, and trading their tokens normally during the maintenance period. The reset does not change XRP’s supply, ownership, or live network operations. For investors, the direct impact on the token’s value is expected to be limited, as the maintenance addresses testing infrastructure rather than the primary ledger.
The announcement comes as XRP traded around $1.03 on November 12, following a weekly decline of more than 15%. While the timing may raise questions about investor confidence, there is no evidence connecting the planned maintenance to XRP’s recent losses. Broader crypto-market sentiment is likely to remain the bigger driver of XRP’s price, though short-term sentiment could suffer if traders confuse the testing networks with the main blockchain.
