August 2021

The rollout is complete, and all systems are online and functional. We apologize for the extended downtime.

We have identified the issue and are almost done resolving it. The system will be back online in a few more minutes.

The rollout is nearly complete. We ran into one issue that we are still resolving. The system may be offline for an additional 30 minutes. We’ll send another status update as soon as we have resolved the issue and brought the system back online.

Our product release is in progress. We will post another update when the release is finished.

We will being our product release on schedule at 8:30pm Mountain Time (in 10 minutes).

We will release a new version of AUTHORWise on August 28, 2021, starting at 8:30 PM Mountain Time. The release will take approximately 90 minutes, during which systems will be offline (including Desktop Application Services, Web Authoring, Reporting, Review Events, Blueprint Surveys, TESTWise, and Data Management). We will focus on test delivery services first, so

We have decided to to reschedule tonight’s release to 08-27-2021 @ 9pm Mountain Time. We are working to reduce the time required to do the release, and also decrease the actual outage time. Additional status updates will be sent early/mid next-week.

We will release a new version of AUTHORWise on August 20, 2021, starting at 9:00 PM Mountain Time. The release will take approximately 2 hours, during which systems will be offline (including Desktop Application Services, Web Authoring, Reporting, Review Events, Blueprint Surveys, TESTWise, and Data Management). We will focus on test delivery services first, so

All systems will be offline for up to 10 minutes on Friday August 13, 2021 starting at 10:00 PM Mountain Time while we perform routine maintenance. Affected AUTHORWise Modules: Desktop Application Services, Web Authoring, Reporting, Review Events, Blueprint Surveys, TESTWise, Data Management

There was an issue that caused our web applications to be intermittently unresponsive for 5 minutes starting at 3:02PM Mountain Time. In some cases, users may have seen a Server 500 error. We were alerted about the issue at 3:02PM by our internal monitoring system, and took immediate action to diagnose and remedy the issue