SentinelOne Outage History
47 incidents recorded over the last 365 days, 20 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded SentinelOne Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 8, 2026 | Sunday maintenance window for version S-26.3.6We have scheduled maintenance during this time. For details, visit Maintenance window schedule: https://community.sentinelone.com/s/article/000008569 | 9h 0m | Scheduled |
| Nov 1, 2026 | Sunday maintenance window for version S-26.3.6The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Oct 25, 2026 | Sunday maintenance window for version S-26.3.5The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Oct 18, 2026 | Sunday maintenance windowThe scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Oct 11, 2026 | Sunday maintenance window for version S-26.3.4The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Oct 4, 2026 | Sunday maintenance window for version S-26.3.4The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Sep 6, 2026 | Sunday maintenance window for version S-26.3.1The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Aug 23, 2026 | Sunday maintenance window for version S-26.2.5 and S-26.3.1The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Aug 9, 2026 | Sunday maintenance window for version S-26.2.6The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Aug 2, 2026 | Sunday maintenance window for version S-26.2.6The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Jul 26, 2026 | Sunday maintenance window for version S-26.2.5The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Jul 19, 2026 | Sunday maintenance window for version S-26.2.5The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Jul 12, 2026 | [EU1, NA1] - Multiple Consoles InaccessibleAll 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. | 5h 21m | Resolved |
| Jul 12, 2026 | Sunday maintenance window for version S-26.2.3The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Jul 6, 2026 | [AP1, AP2, AP3, EU1, EU2, EU3, ME1, NA1, NA2, NA3, NA4] - Delayed Data IngestionServices have been restored, and we are working to validate the health of your systems. While data ingestion has resumed, there is a temporary backlog of data still being processed. As systems catch up, you may see a… | 8h 52m | Resolved |
| Jun 28, 2026 | Sunday maintenance window for version S-26.2.3The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Jun 21, 2026 | Sunday maintenance window for version S-26.2.3The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Jun 14, 2026 | Sunday maintenance window for version S-26.2.2The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Jun 7, 2026 | Sunday maintenance window for version S-26.2.2The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Jun 5, 2026 | [AP1] - Delayed Data IngestionAll 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. | 1h 28m | Resolved |
| Jun 2, 2026 | [EU1] - Delayed Data IngestionAll 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. | 50 min | Resolved |
| May 17, 2026 | Sunday maintenance window for version S-26.1.6The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| May 10, 2026 | Sunday maintenance window for version S-26.1.6The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| May 8, 2026 | [NA1] Service InterruptionAll 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. | 13h 32m | Resolved |
| May 3, 2026 | Sunday maintenance window for version S-26.1.6The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Apr 26, 2026 | Sunday maintenance windowThe scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Apr 19, 2026 | Sunday maintenance window for version S-26.1.5The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Apr 12, 2026 | Sunday maintenance window for version S-26.1.2The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Apr 6, 2026 | [EU1] Delayed Data IngestionAll 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. | 3h 59m | Resolved |
| Mar 31, 2026 | [ME1] Delayed Data IngestionAll 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. | 1h 4m | Resolved |
| Mar 29, 2026 | Sunday maintenance window for version S-26.1.3The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Mar 22, 2026 | Sunday maintenance window for version S-26.1.3The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Mar 15, 2026 | Sunday maintenance window for version S-26.1.2The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Mar 8, 2026 | Sunday maintenance window for version S-26.1.2The scheduled maintenance has been completed. | 9h 0m | Scheduled |
| Mar 4, 2026 | [NA1] Delayed Data IngestionAll 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. | 53 min | Resolved |
| Feb 13, 2026 | [NA1] Delayed Data IngestionAll 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. | 2h 40m | Resolved |
| Feb 12, 2026 | [EU1] Delayed Data IngestionAll 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. | 4h 31m | Resolved |
| Feb 3, 2026 | [EU1] Partial Platform DisruptionAll 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. | 3h 12m | Resolved |
| Feb 2, 2026 | Elevated False Positive Alert ActivityAll 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. | 3h 49m | Resolved |
| Jan 29, 2026 | [NA1] Partial Service DisruptionAll 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. | 3h 7m | Resolved |
| Jan 27, 2026 | NA1 Multiple Consoles DownAll 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. | 50 min | Resolved |
| Jan 20, 2026 | EventDB and SDL experiencing partial outageAll 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. | 1h 55m | Resolved |
| Dec 15, 2025 | [EU1] intermittent console log in errorsAll 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. | 42 min | Resolved |
| Dec 12, 2025 | [NA1] Degraded Performance on SOCAll 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. | 1h 16m | Resolved |
| Dec 4, 2025 | US-EAST-01 ConsolesAll 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. | 2h 2m | Resolved |
| Nov 10, 2025 | [NA1] Console degraded performanceWe’re aware that multiple agents were showing as offline in the management console. Our engineers investigated and restored connectivity. During this time, your endpoints were protected, though management actions may… | 0 min | Resolved |
| Nov 6, 2025 | [NA1] Delayed Data IngestionAll 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. | 53 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next SentinelOne incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This SentinelOne Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before SentinelOne acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single SentinelOne outage in this window ran 13h 32m, against a mean recovery of 6h 28m. If you depend on SentinelOne in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.