Vendor reports: operationalResolved · vendor status “resolved”Official status API
Entitlements is currently experiencing a service disruption in US-GOV-West-1
Reported by SailPoint · Identity & Security · source last read 4 min ago
- Vendor start
- May 19, 2026, 21:22 UTC
- Vendor's clock
- Resolved
- May 19, 2026, 22:04 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 42 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Regions: us-gov-west-1 (read from the title, so inferred).[E5]
What is unknown
- Which components are affected: the vendor did not say.[E6]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-05-19 22:04 UTC · summary s1, evidence 674f615e15b2dd36
Evidence (7)
- E1SailPoint reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Entitlements is currently experiencing a service disruption in US-GOV-West-1". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-05-19 21:22 UTC. (vendor) source (opens in a new tab)
- E5Regions written in the title (inferred): us-gov-west-1. (Statuswall) source (opens in a new tab)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-05-19 22:04 UTC. (vendor) source (opens in a new tab)
Affected scope
us-gov-west-1
Components: not stated by the vendor
Read from region codes written in the incident title, so treat it as inferred.
Potential relevance
SailPoint is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- May 19, 2026, 21:22 UTCVendor-reported startVendor time
- May 19, 2026, 22:04 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.