Degraded processing rates on some backend systems in US-East-1
Incident Report for SailPoint
Resolved
This incident has been resolved.
Posted Jan 28, 2022 - 03:44 UTC
Update
As of 5PM central time we are continuing to monitor improvements in queue processing. Types of data may be behind including search and audit, but these events are updating. We apologize for any inconvenience this may cause and we are working diligently to resolve the issue as quickly as possible.
Posted Jan 27, 2022 - 23:13 UTC
Update
We have scaled up several backend systems and are continuing to monitor improvements in queue processing.
Posted Jan 27, 2022 - 21:45 UTC
Update
A mitigation is in place, however some backend systems are still catching up on delayed work. Types of data may be behind including search and audit, but these events are updating. We are working diligently to safely increase resources to resolve the issue as quickly as possible.
Posted Jan 27, 2022 - 14:32 UTC
Monitoring
A potential resolution is in place. We are continuing to monitor the issue and presently resources have been added to process the backlog.
Expectation is all services should be up to date by start of business AMS.
Posted Jan 27, 2022 - 07:47 UTC
Update
All relevant teams engaged as we continue to work on a fix for this issue. This issue affects multiple aspects of our platform. Several types of data may be behind including search and audit. Emails from our platform will also be delayed.
We have identified the problem and are working to resolve it.
Posted Jan 27, 2022 - 06:11 UTC
Update
All relevant teams engaged as we continue to work on a fix for this issue.
Posted Jan 27, 2022 - 05:17 UTC
Update
We are continuing to work on a fix for this issue.
Posted Jan 27, 2022 - 04:09 UTC
Identified
We are currently experiencing degraded processing rates on several backend systems. This affects multiple aspects of our platform. Several types of data may be behind including search and audit. Emails from our platform may also be delayed. We have identified the problem and are working to resolve it.
Posted Jan 27, 2022 - 02:14 UTC
This incident affected: Provisioning (N. Virginia us-east-1), Access Request (N. Virginia us-east-1), Aggregation (N. Virginia us-east-1), Search (N. Virginia us-east-1), and Emails (N. Virginia us-east-1).