Upcoming product maintenance and downtime

Update:

We wish to inform you that after further testing and validation work on this upcoming migration, we have identified potential concerns that require additional time to resolve. As such, we're postponing the migration of our US-East-1 Production environment. This decision, made out of caution, aims to ensure the uninterrupted processing of your critical events. Consequently, the scheduled downtime for this Sunday, Feb 25 at 1am CST, will not occur. A new migration date will be announced once thorough testing is complete, guaranteeing no less than two weeks' notice and aiming for minimal disruption during a weekend US nighttime. These concerns have no impact on other environments that have already been migrated, so no additional actions are necessary at this time.

We apologize for any inconvenience this may cause, especially to those who have prepared for the initial migration date. Ensuring the performance and stability of our services remains our utmost priority. Rest assured, we will provide updates and communicate the new migration schedule as soon as possible. Thank you for your understanding and continued support.

Original notification:

We are performing an upgrade of a key backend messaging system in all regions starting February 12th, 2024. Each hosting environment will experience 2-4 hours of downtime during its scheduled maintenance window, see below.

This upgrade will enable SailPoint’s Identity Security Cloud to keep scaling to support our ever-growing set of customers and features. To prevent data or message loss, we will shut down all products in the environment being upgraded for the duration of the migration (2-4 hours). This is to make sure that there are no messages in flight that may get lost or misrouted as we switch our components to start using the upgraded cluster for messaging.

During the maintenance window, we will first shutdown all frontend and backend services in the environment as well as all AI pipelines. We will then ensure that all data is replicated to the new cluster and that no new messages are flowing. Once there, we will reconfigure all components to use the new cluster and start up the environment.

We have tested this migration in our lower environments and have developed and tested rollback processes as well in case of unexpected setbacks.

The maintenance schedule is as follows. We will keep this table up to date if the schedules changes. Please reach out to your CSM or our Support team if you have any questions.

More additional information, please navigate to https://developer.sailpoint.com/discuss/t/upcoming-product-maintenance-and-downtime/28620.