Changes / SentinelOne / [NA1] Partial Service Disruption
SentinelOne: Major incident: [NA1] Partial Service Disruption
Summary
SentinelOne reported a major partial service disruption affecting Singularity Operations Center and Management Console - USA (NA1), with intermittent connectivity issues. It started at 2026-01-29 18:08 UTC and was resolved at 2026-01-29 21:15 UTC, lasting 3 h 7 min. SentinelOne applied a fix and confirmed all services were fully restored.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: [NA1] Partial Service Disruption
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-01-29 18:08 UTC
Before: not present
After: 2026-01-29 21:15 UTC
Before: not present
After: Singularity Operations Center and Management Console - USA (NA1), USA (NA1)
Before: not present
After: The underlying issue has been identified and a fix has been implemented. We will continue to observe for any further issues and will keep you updated on progress. We appreciate your patience as we resolve the incident.
Before: not present
After: A fix has been applied and we are closely monitoring system performance to ensure stability. You may experience intermittent connectivity issues while the situation continues to improve. We will observe for any further issues and will keep you updated on progress.
Before: not present
After: All services have been fully restored and the incident is now resolved. We have validated that all systems are functioning normally. Thank you for your patience throughout this incident.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: [NA1] Partial Service Disruption (this change) SentinelOne reported a major partial service disruption affecting Singularity Operations Center and Management Console - USA (NA1), with intermittent connectivity issues. It started at 2026-01-29 18:08 UTC and was resolved at 2026-01-29 21:15 UTC, lasting 3 h 7 min. SentinelOne applied a fix and confirmed all services were fully restored. | Major incident |
All SentinelOne changes → · SentinelOne profile · Markdown · JSON