SailPoint incident

Identity Security Cloud is currently facing a service disruption that is affecting the separation of duties policy.

Minor Resolved View vendor source →

SailPoint experienced a minor incident on January 23, 2026 affecting N. Virginia us-east-1 and Frankfurt eu-central-1 and 1 more component, lasting 2h 6m. The incident has been resolved; the full update timeline is below.

Started
Jan 23, 2026, 10:07 AM UTC
Resolved
Jan 23, 2026, 12:14 PM UTC
Duration
2h 6m
Detected by Pingoru
Jan 23, 2026, 10:07 AM UTC

Affected components

N. Virginia us-east-1Frankfurt eu-central-1London eu-west-2Sydney ap-southeast-2

Update timeline

  1. investigating Jan 23, 2026, 10:07 AM UTC

    SailPoint is investigating an issue with Identity Security Cloud that is currently impacting some customers, who are unable to save separation of duty policies. We are working to address the service disruption and will provide an update once it is resolved.

  2. investigating Jan 23, 2026, 10:08 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jan 23, 2026, 12:14 PM UTC

    The SailPoint team has mitigated the service disruption affecting the Separation of Duties policy in Identity Security Cloud.