Update - We've now processed all of the affected DOIs. We have reverted all of the inadvertently updated resource resolution URLs. The script completed its run at 20:14 UTC, Thursday, 22 July.
Jul 22, 20:35 UTC

Update - We're nearly 48 hours into our run in production to revert the resource resolution URLs of the DOIs affected by this issue. There are still no errors, and we have processed over 706,000 DOIs (well over half). We're on track to have all affected DOIs reverted by late Thursday/early Friday of this week.
Jul 21, 18:49 UTC

Update - We're over 24 hours into our run in production to revert the resource resolution URLs of the DOIs affected by this issue. So far we haven't had any problems and have processed over 320,000 DOIs. Based on this rate, all affected DOIs should be reverted by late Thursday/early Friday of this week.
Jul 20, 21:31 UTC

Update - We have begun reverting the resource resolution URLs of the DOIs affected by this issue.
Jul 19, 20:50 UTC

Update - Good news! Our third full test run of our script is error free. We will begin reverting resource resolution URLs for the 22 members affected by this error starting today.
Jul 19, 19:02 UTC

Update - We have completed two test runs to revert the resource resolution URLs of the DOIs affected by this mistake. Both tests have gone well, but turned up problems with our reversion script. We're currently running a third test run and will begin reviewing the results of that test later today. While we'd love to get the reversions to production resource resolution URLs kicked off as soon as possible and revert all of the mistakes now, we have decided that running additional tests is the best option for all affected members. Thus, we will not begin the reversion on production resource resolution URLs until Monday, 19 July at the earliest.
Jul 16, 18:28 UTC

Update - We are currently going through the results of our test run to revert all of the affected DOIs' resource resolution URLs to ensure there are no errors in our script. If that review goes smoothly, we should be able to begin the reversions in production starting tomorrow.
Jul 15, 19:33 UTC

Update - Our technical team continues to work on testing the URL reversion script to ensure that it is making the desired reversions and only the desired reversions to the affected content. We'll begin reviewing test results as a team tomorrow and hope to kick off the resource resolution URL reversions of the affected DOIs on Friday, 16 July.
Jul 14, 17:17 UTC

Update - Our technical team will begin testing their script to revert the affected resource resolution URL later today. We're still looking at the second half of the week before we begin making URL reversions. We have also confirmed the list of all affected DOIs and will be sharing that with the 22 affected members shortly.
Jul 13, 16:39 UTC

Update - Our technical team is continuing to work on a fix. We're anticipating reverting the incorrect resource resolution URLs of the over 1.1 million affected DOIs during the second half of this week. This is the first time we're attempting a reversion of resource resolution URLs, so we're taking our time to ensure we get it right.
Jul 12, 14:53 UTC

Update - We are continuing to investigate this issue.
Jul 20, 17:14 UTC