Ripple to Wipe XRP Ledger Testnet and Devnet on Nov. 25 After Server Failure

Ripple's XRP Ledger Operations team will reset the XRPL Testnet and Devnet on Nov. 25, erasing all test accounts and transaction histories after a storage-server failure the company says it cannot recover from without wiping the data.

The scheduled window runs one hour, from 8 p.m. to 9 p.m. ET on Nov. 25 — 01:00 to 02:00 UTC on Nov. 26. The trigger is technical, not routine: the server holding Testnet's transaction history failed, and Ripple has determined that recovery is impossible without clearing the existing dataset. Rather than leave the testing environment in a degraded state, the team chose a full reset.

What gets erased in the reset?

The wipe touches every layer of the two test environments. According to Ripple's announcement, the reset will remove:

• Test accounts created on either network
• Faucet-funded balances, meaning developers lose their test tokens
• Full transaction histories on both networks
• Automated market maker (AMM) configurations
• Escrow arrangements set up for testing
• Order book configurations

Developers who rely on Testnet or Devnet will need to rebuild their test suites from scratch and request fresh test tokens through the faucet once the networks come back online.

Why AMM users face extra work

One operational detail stands out for teams building on XRPL's automated market maker feature. When developers recreate AMM pools after the reset, those pools will live under new account addresses. Any application that references hard-coded pool addresses will break and must be updated. Teams that abstracted address handling won't feel the change; those that didn't have a maintenance task on their hands before Nov. 25.

What stays in place?

The reset's blast radius is deliberately narrow. Ripple has confirmed the following elements will not change:

• Public network URLs remain the same
• Network IDs for both environments stay in place
• Validator settings carry over unchanged
• Testnet amendment statuses reset to match Mainnet's current state

Ripple also plans to use the maintenance window to increase the server's storage capacity — an implicit acknowledgment that the failed hardware was undersized for the transaction history it was asked to hold. Expanding capacity should reduce the odds of a repeat failure, though the company did not specify the new storage footprint.

Mainnet is untouched

For XRP holders, the operational takeaway is simple: nothing on Mainnet changes. Mainnet transaction records, XRP balances and real tokens held in users' wallets all remain intact, since the reset applies only to the sandbox environments developers use for testing.

The reset also spares adjacent infrastructure. Xahau, the XRPL sidechain, sits outside the operation, and Hooks Testnet — the experimental environment for the Hooks smart-contract feature — is likewise excluded.

Developers with active Testnet or Devnet deployments have until the 8 p.m. ET Nov. 25 window to export whatever test data or configuration references they want to preserve. After that hour, the slate is clean, the AMM addresses are new, and every hard-coded reference in the ecosystem's test builds becomes a bug waiting to surface.