Live / SailPoint / Incident
SailPoint: Identity Security Cloud entitlement delays in Search and Request Center US-East-1
SailPoint · sailpoint.comMinor incidentResolved2026-10-05 02:36 UTC
Public — what happened
Summary
SailPoint said that starting September 29, 2026 at 14:55 UTC, newly collected or changed entitlements were slow to be indexed and show up in the Search and Search Lite tools of Identity Security Cloud in its US-East-1 region. The company reported working through a large backlog of data over the following day, put a fix in place on September 30, and said on October 1 that the backlog was cleared and real-time activity was no longer delayed, though it was still finishing work so entitlement reporting would be fully accurate. On October 2 SailPoint said it had found further effects on entitlements and kept working on them, and the incident was marked resolved on October 5 at 02:36. The company did not publicly name a cause.
Affected
N. Virginia us-east-1
Timeline
- Started — 2026-09-29 14:55 UTC
- Investigating — 2026-09-29 14:55 UTC (4 updates)
- Identified — 2026-09-30 11:39 UTC
- Monitoring — 2026-09-30 21:51 UTC (2 updates)
- Identified — 2026-10-02 13:15 UTC (2 updates)
- Resolved — 2026-10-05 02:36 UTC · 5 days 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 41, 2026, our weekly internet health report.