XRP Ledger Testnet and Devnet reset on 25 November 2026: what is wiped and what developers need to do

The XRP Ledger (XRPL) has two public test networks run by Ripple: Testnet and Devnet. Both will be reset on Wednesday, 25 November 2026, according to an announcement on the official developer site dated 9 November (xrpl.org blog). A reset deletes all ledger data on these two networks. The production network, Mainnet, keeps running as usual (xrpl.org blog).

Below: what is being reset, why, what developers and server operators should do, and what stays untouched.

The official post gives the date: Wednesday, 25 November 2026 (xrpl.org blog). It does not give a time of day.

A time window appeared in news coverage. Citing the XRPL Operations account, one report says the reset will happen between 5 PM and 6 PM Pacific Time (Coin Alert News). On 25 November, Pacific Time is UTC−8 (standard time). That window therefore equals 01:00–02:00 UTC on Thursday, 26 November 2026. This conversion is our own. The window itself comes from secondary reporting, not from the xrpl.org post.

Both networks are reset together. The reset will delete all ledger data in Testnet and Devnet. The post lists accounts, transactions, balances, settings, offers, AMMs and escrows, plus "other data" (xrpl.org blog).

XRPL documentation describes one production network, Mainnet, and several alternative networks (xrpl.org, Parallel Networks).

• Testnet runs stable releases. It is a testing ground for software built on the XRP Ledger. Its amendment status is meant to closely mirror Mainnet.
• Devnet runs beta releases. It is a preview of features and amendments that are not yet enabled on Mainnet.

Each of these networks has its own supply of test XRP. Test XRP is given away for free through a faucet. According to the documentation, it has no real-world value and is lost when the network is reset (xrpl.org, Parallel Networks).

The same page explains why resets are possible at all. Ripple runs the main servers in Testnet and Devnet. These networks do not use a diverse, censorship-resistant set of validators. This makes it possible for Ripple to reset them at any time (xrpl.org, Parallel Networks).

The stated reason is technical. Testnet relied on a single full history server. That server crashed and cannot be recovered without a reset (xrpl.org blog).

To avoid a repeat, Ripple says it is upgrading server storage capacity. The post adds that some retention limits will remain, but the upgrade should reduce how often Testnet needs to be reset (xrpl.org blog).

Resets are not new. Earlier posts on the same site give other reasons:

• August 2024, Testnet: to improve stability and reduce the cost of running a Testnet node. The post said free test XRP allowed resource-heavy activity, such as minting millions of NFTs (xrpl.org blog, 2024).
• 3 March 2026, Devnet: the Batch amendment was set to unsupported in version 3.1.1. Devnet had to be reset so that validators upgrading to that version would not become amendment blocked (xrpl.org blog, rippled 3.1.1).

The 2024 post also gives a general reason. Networks are occasionally reset so the faucet can keep giving out test XRP, and so test balances have no real-world value (xrpl.org blog, 2024).

The steps below follow the official post (xrpl.org blog).

1. Re-fund accounts. Any account you use on Testnet or Devnet will be gone. Get new test XRP from the faucet (xrpl.org, Faucets) and re-create the accounts.
2. Re-create other objects. Trust lines, offers, escrows, AMMs and other setup must be built again.
3. Fixed addresses. If your code relies on specific addresses, you can ask the faucet to fund the same address again.
4. AMM addresses change. AMMs re-created after the reset will generally have different account addresses. Code or configuration that stores an AMM address needs updating.
5. Keys. The post repeats a standing rule: do not use the same addresses or key pairs on Mainnet and any test network.

After the reset, Testnet's amendment statuses will be restored to match Mainnet (xrpl.org blog). For tests that depend on a specific amendment, it is worth checking its status on Testnet again once the network is back. Devnet, by design, previews features not yet enabled on Mainnet (xrpl.org, Parallel Networks).

If you run an xrpld server connected to Testnet or Devnet, the post says you should delete its database data and restart it after the reset. The database locations are set in the config file under [database_path] and [node_db]. For a default setup, the post lists three commands (xrpl.org blog):

sudo systemctl stop xrpld
sudo rm -r /var/lib/xrpld/db/*
sudo systemctl start xrpld

The important URLs, Network ID and validator settings for both networks stay the same. Connection settings do not need to change (xrpl.org blog).

• Mainnet. The resets affect Testnet and Devnet only. Other networks, including Mainnet, continue to operate as usual (xrpl.org blog).
• Real XRP balances. Mainnet accounts and balances are not touched. Only test XRP is deleted, and test XRP has no real-world value (xrpl.org, Parallel Networks).
• Connection details. URLs, Network ID and validator settings remain unchanged (xrpl.org blog).
• Other altnets. News coverage lists Xahau and the Hooks Testnet as unaffected (Coin Alert News).

• The xrpl.org post does not state a time of day. The 17:00–18:00 Pacific window comes from news coverage.
• The post does not say how long the networks will be offline.
• It does not say what the new retention limits on Testnet will be.

• xrpl.org – Upcoming Testnet and Devnet Resets (9 November 2026)
• xrpl.org – Parallel Networks
• xrpl.org – XRP Faucets
• xrpl.org – Introducing XRP Ledger version 3.1.1 and Upcoming Devnet Reset
• xrpl.org – Upcoming Testnet Reset (2024)
• Coin Alert News – XRPL Testnet and Devnet to Be Reset on November 25 (10 November 2026)

Educational content. Not investment advice.