Live / SailPoint / Incident
SailPoint: Staging - Access Requests are delayed in processing
SailPoint · sailpoint.comMinor incidentResolved2026-11-04 08:35 UTC
Public — what happened
Summary
SailPoint said that in its staging environment, which is a testing area, access requests were being accepted but were slow to be processed. The company began investigating at 20:20 UTC on 2026-11-03 and rated the issue as minor. About an hour and fifteen minutes later it said it had found the problem and was working on a fix, and by 22:03 UTC it said a fix was in place and it was monitoring. SailPoint marked the incident resolved at 08:35 UTC on 2026-11-04.
Affected
N. Virginia us-east-1, Oregon us-west-2
Timeline
- Started — 2026-11-03 20:20 UTC
- Investigating — 2026-11-03 20:20 UTC
- Identified — 2026-11-03 21:35 UTC
- Monitoring — 2026-11-03 22:03 UTC
- Resolved — 2026-11-04 08:35 UTC · 12h 15m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach SailPoint against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for SailPoint: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the SailPoint report →
More from SailPoint
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.