SailPoint logo

Is SailPoint down?

No reported issues

From status.sailpoint.com · checked 2 minutes ago · every 5 minutes

Get alerts for SailPoint

An email when it goes down, and when it’s back.

As of 03:33 UTC on 12 November 2026, SailPoint's status page reports no issues. Its last reported problem was on 10 November 2026: “Identity Security Cloud is currently experiencing a service disruption”, issue, for 1 h from 20:52 UTC.

Last problem
10 Nov · 1 h
Problems, last 30 days
3
Typical incident
12 h 15 min
Longest in 90 days
5 days · 29 Sept

Uptime

SailPoint, last 30 days

94.99 %

100%62.5%25%
Oct 14 Today

Biggest dip: SailPoint, 21.7 h of issue on Nov 4.

Incidents

Started in the last 7 days

1

210
FSSMTWToday

This week Week before

Latest: SailPoint, issue on Nov 10.

Recovery

Median time back online

12 h 15 min

21 h 45 min0
30 days ago Today

0 of 3 were over within an hour. Each dot is one incident; the dashed line is the median.

Components 216

All online

Provisioning 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Access Request 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Password Management 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Access Certification 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Separation of Duty 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Aggregation 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Nightly Refresh 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Search 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Tags 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Emails 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Workflows 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Access Modeling 8 parts
  • N. Virginia us-east-1
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • FedRAMP us-gov-west-1
Access Insights 9 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • FedRAMP us-gov-west-1
Recommendations 9 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • FedRAMP us-gov-west-1
CAM - Unused Access 5 parts
  • N. Virginia us-east-1
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
CAM - Alerts 5 parts
  • N. Virginia us-east-1
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
CAM - Unused Access Reporting 5 parts
  • N. Virginia us-east-1
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
CAM - Identities/Objects 5 parts
  • N. Virginia us-east-1
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
NERM 9 parts
  • N. Virginia us-east-1
  • Frankfurt eu-central-1
  • Ireland eu-west-1
  • London eu-west-2
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • FedRAMP us-gov-west-1
ARM - Analysis Services 2 parts
  • Virginia East US 2
  • Ireland North Europe
ARM - Realtime What-If Simulation 2 parts
  • Virginia East US 2
  • Ireland North Europe
ARM - Reporting Services 2 parts
  • Virginia East US 2
  • Ireland North Europe
ARM - Emergency Access Management 2 parts
  • Virginia East US 2
  • Ireland North Europe
ARM - Access Reviewer 2 parts
  • Virginia East US 2
  • Ireland North Europe
Identity Security Cloud User Interface 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1
Access Intelligence Center 8 parts
  • US
  • EU
  • UK
  • DE
  • Asia Pacific - Sydney
  • Asia Pacific - Singapore
  • Asia Pacific - Japan
  • FedRAMP us-gov-west-1
Data Access Security 11 parts
  • N. Virginia us-east-1
  • Oregon us-west-2
  • Frankfurt eu-central-1
  • London eu-west-2
  • Sydney ap-southeast-2
  • Canada ca-central-1
  • Tokyo ap-northeast-1
  • Singapore ap-southeast-1
  • Mumbai ap-south-1
  • São Paulo sa-east-1
  • FedRAMP us-gov-west-1

Last 90 days

6 incidents in 48 days tracked · no reported issues 85.3% of the time · typical incident 12 h 15 min

Aug 15 Today (UTC)

Recent incidents

Times in UTC

  1. Issue
    Identity Security Cloud is currently experiencing a service disruption 1 h
  2. Issue
    FedRamp - Updates to Entitlement and Access Profiles are not being reflected in the UI 21 h 45 min
  3. Issue
    Staging - Access Requests are delayed in processing 12 h 15 min
  4. Issue
    NERM is currently experiencing a service disruption 41 min
  5. Issue
    Ping SSO Outage: Users experiencing sign-in issues 2 h 30 min
  6. Issue
    Identity Security Cloud entitlement delays in Search and Request Center US-East-1 and 1 more 5 days
All incidents on status.sailpoint.com ↗

Where this comes from

Stackpulse reads SailPoint’s official status page at status.sailpoint.com every 5 minutes and keeps 90 days of what changed. We don’t test SailPoint ourselves, so a problem shows here once SailPoint reports it.

Stackpulse isn’t affiliated with SailPoint. Names and logos belong to their owners.

For agents and scripts

The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.