SailPoint incident

Identity Security Cloud is currently experiencing a service disruption.

Major Resolved View vendor source →

SailPoint experienced a major incident on February 24, 2026 affecting N. Virginia us-east-1 and Oregon us-west-2 and 1 more component, lasting 1h 16m. The incident has been resolved; the full update timeline is below.

Started
Feb 24, 2026, 02:16 PM UTC
Resolved
Feb 24, 2026, 03:32 PM UTC
Duration
1h 16m
Detected by Pingoru
Feb 24, 2026, 02:16 PM UTC

Affected components

N. Virginia us-east-1Oregon us-west-2Frankfurt eu-central-1London eu-west-2Sydney ap-southeast-2Canada ca-central-1Tokyo ap-northeast-1Singapore ap-southeast-1Mumbai ap-south-1UAE me-central-1

Update timeline

  1. investigating Feb 24, 2026, 02:16 PM UTC

    SailPoint is investigating an issue with Identity Security Cloud that is currently impacting some of our customers. We are working on addressing the service disruption and will provide an update upon resolution.

  2. identified Feb 24, 2026, 02:38 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Feb 24, 2026, 03:13 PM UTC

    The fix continues to be implemented and is 90% complete.

  4. monitoring Feb 24, 2026, 03:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Feb 24, 2026, 03:32 PM UTC

    The SailPoint team has mitigated the service disruption with Identity Security Cloud.