Progress -- 66% of nodes are now upgraded to rippled 2.3.0! If you haven’t yet, please upgrade your infra to ensure continued operation of your server. While the bug poses less risk to the network now, sharing more technical details at this stage could still affect users who haven’t upgraded. We will share a full incident report once at least 80% of the network has upgraded.

Currently, ~60% of XRPL nodes (436 of 715) have upgraded to rippled 2.3.0. If you haven’t upgraded yet, please do so ASAP to ensure continued operations of your server!

As promised – an update on the cause of the XRP Ledger’s 10 min pause earlier this week, details on how the fix was developed and what’s next. And, if you haven’t already upgraded your XRPL infra to 2.3.0, please do so ASAP! Thank you to all across the community who work day in and day out to keep the XRPL safe, secure and reliable.

XRPL node operators and validators - please update your infra to the 2.3.0 rippled release ASAP, and big thanks to all who worked quickly to release a fix. Given the nature of the issue, more details on the root cause to come *after* the network adopts the fix (to ensure safety).

The RippleX Eng team is investigating the root cause and working on a fix – appreciate @XRPLLabs and the rest of the community’s quick responses to make sure the XRP Ledger is secure and stable. We’ll share more updates as soon as we have additional information.

Update: Most nodes are back on a consensus ledger and closing ledgers again. The Full History nodes are syncing fully back, meaning no ledgers seem to have been lost :) Network seems to recover on its own. Full History nodes are still syncing back, other than that we're pretty much back to normal.