SailPoint incident

Access Request is currently experiencing a service disruption.

Minor Resolved View vendor source →

SailPoint experienced a minor incident on May 12, 2026 affecting N. Virginia us-east-1 and Oregon us-west-2 and 1 more component, lasting 38m. The incident has been resolved; the full update timeline is below.

Started
May 12, 2026, 03:28 PM UTC
Resolved
May 12, 2026, 04:06 PM UTC
Duration
38m
Detected by Pingoru
May 12, 2026, 03:28 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-1São Paulo sa-east-1

Update timeline

  1. investigating May 12, 2026, 03:28 PM UTC

    SailPoint is investigating an issue with Access Request feature 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 May 12, 2026, 04:06 PM UTC

    The issue is has been identified and a fix has been implemented. All production regions are working as normal but some staging environments are still in progress to get fixed.

  3. resolved May 12, 2026, 04:06 PM UTC

    This incident has been resolved.