Overview

 

In most cases, maintenance has limited or no negative impact on the availability and functionality of our application services. We endeavor to provide at least five days advance notice of any unplanned maintenance outside of the defined maintenance windows. In addition, we may perform emergency unscheduled maintenance at any time. If we expect emergency unscheduled maintenance to negatively affect the availability or functionality of the Services, we will use professionally reasonable efforts to provide advance notice.

Default Maintenance Windows

Unless otherwise arranged, these are our standard maintenance windows:

Continuous changes a​re those where stable automated testing and deployment processes manage the commits, including platform critical updates as well as configuration and code deployments. Ready and Student use a complete continuous delivery model where changes are deployed through staging to production as soon as they are tested and ready.  For Research the changes are staged for deployment at certain times:


  5:00 PM (1700) US/Mountain Daily - Changes are committed to Staging environments.
  8:00 PM (2000) US/Mountain Daily - The same changes validated in Staging are committed to Production environments.


And the same for Financials, but at different times:


  5:00 PM (1700) US/Mountain Thursday - Changes are committed to Staging environments.
12:00 AM (0000) US/Mountain Thursday - The same changes validated in Staging are committed to Production environments.


Standard changes may not be used, but are reserved for updates which cannot fit the Continuous Change cycle.

 3rd Sunday, 5:00 PM (1700) US/Mountain to 12:00 AM (0000) US/Mountain.


Short-fuse changes outside of these windows may be made with at least 5 business days notification.