SailPoint experienced a minor incident on June 16, 2026 affecting N. Virginia us-east-1, lasting 3d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 16, 2026, 07:23 PM UTC
We are currently experiencing degraded performance with our search functionality in the us-east-1 region, resulting in delays. Our team is actively investigating the issue and working toward a resolution. We will provide an update when available.
- investigating Jun 16, 2026, 08:17 PM UTC
We are continuing to investigate.
- investigating Jun 16, 2026, 11:33 PM UTC
Our team is continuing to investigate the cause of the degraded search performance in the us-east-1 region.
- investigating Jun 17, 2026, 02:58 AM UTC
The degraded performance affecting search functionality in the us-east-1 region is ongoing. Our engineers are actively working to resolve the issue.
- investigating Jun 17, 2026, 07:06 AM UTC
The degraded performance impacting search functionality in the us-east-1 region remains active. Our engineers are continuing their work to implement a resolution.
- investigating Jun 17, 2026, 10:27 AM UTC
We are still actively working on this issue. Our engineers continue their efforts to restore full search functionality in the us-east-1 region.
- identified Jun 17, 2026, 02:10 PM UTC
We are continuing our work to restore full search functionality in the us-east-1 region. The system is currently processing a backlog of data, and we estimate we are about 16 hours from being fully caught up. While we do not yet have a definitive timeline for complete resolution, some customers may begin to notice performance improvements throughout the day. Our team remains actively engaged.
- identified Jun 17, 2026, 05:57 PM UTC
We continue to monitor processing. Previous guidelines for estimated ETA remain intact.
- identified Jun 17, 2026, 08:34 PM UTC
Update - Processing of the search data backlog is ongoing. We have adjusted our estimate and are now approximately 17 hours from being fully caught up. While we do not have a hard timeline for full resolution, incremental improvements should continue to be visible to some customers throughout the afternoon and overnight.
- identified Jun 18, 2026, 01:27 AM UTC
We continue to process the search data backlog and are seeing good progress. System performance will gradually improve as we work toward full recovery.
- identified Jun 18, 2026, 07:40 AM UTC
Search data processing is progressing, and customer impact continues to decline. However, due to the volume of the backlog, we will not meet our previously shared recovery timeline. We are continuing to work through the remaining data and will provide further updates as recovery progresses.
- identified Jun 18, 2026, 05:24 PM UTC
Search data processing is actively progressing. However, due to the volume of the backlog, we will not meet the previously shared recovery timeline. Our teams remain focused on processing the remaining data, and we will provide further updates as recovery continues.
- identified Jun 19, 2026, 04:18 AM UTC
The recovery efforts for search data processing are progressing smoothly. Our engineering and operations teams remain fully engaged, working diligently to safely clear the remaining data.
- identified Jun 19, 2026, 06:52 PM UTC
We apologize for the continued search degradation in the us-east-1 region. Our engineering teams have resolved the core issue and are currently working around the clock to process the resulting data backlog. We expect the issue to be resolved by end of day 6/19/26. As our systems safely work through this queue, you will begin to see gradual, incremental improvements in search performance. We understand the impact this disruption has on your daily operations and appreciate your patience. Supporting your business continuity remains our top priority, and we are fully committed to delivering the reliable, enterprise-grade service and transparent communication that you count on from us.
- resolved Jun 19, 2026, 11:08 PM UTC
This incident is now resolved. Our engineering teams have resolved the core issue and the resulting backlog is fully processed.