SentinelOne

Affected: USA (NA1), USA (NA1), USA (NA1), USA (NA1), USA (NA1), USA (NA1), Germany (EU1), Germany (EU1), Germany (EU1), Germany (EU1), Germany (EU1), Germany (EU1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-12 11:36 UTC

   We are aware of the ongoing service interruption and are actively investigating the root cause. We apologize for the inconvenience and appreciate your patience as we work to resolve the issue.

2. investigating 2026-07-12 12:00 UTC

   We are aware of the ongoing service interruption during which time your console may be inaccessible. We are actively investigating the root cause. We apologize for the inconvenience and appreciate your patience as we work to resolve the issue.

3. identified 2026-07-12 14:37 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

4. resolved 2026-07-12 16:58 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA4), Canada (NA3), Germany (EU1), Germany (EU2), Singapore (AP1), Australia (AP2), India (AP3)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-06 06:58 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. identified 2026-07-06 10:23 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. resolved 2026-07-06 15:50 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Singapore (AP1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-05 09:03 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. investigating 2026-06-05 09:27 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. investigating 2026-06-05 09:37 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. resolved 2026-06-05 10:32 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Germany (EU1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-02 09:43 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. identified 2026-06-02 10:08 UTC

   To be updated

3. monitoring 2026-06-02 10:21 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. resolved 2026-06-02 10:33 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), USA (NA1), USA (NA1), USA (NA1), USA (NA1)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 02:05 UTC

   SentinelOne is closely monitoring the ongoing degradation of an AWS Availability Zone that is impacting SentinelOne services in NA1. During this time, you may experience temporary service disruption. We will provide further details as this situation progresses.

2. identified 2026-05-08 02:32 UTC

   SentinelOne is closely monitoring the ongoing degradation of an AWS Availability Zone that is impacting SentinelOne services in NA1. During this time, you may experience temporary service disruption. We will provide further details as this situation progresses.

3. resolved 2026-05-08 15:38 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Germany (EU1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-06 17:20 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. investigating 2026-04-06 18:40 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-04-06 19:56 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

4. resolved 2026-04-06 21:19 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: KSA (ME1), KSA (ME1), KSA (ME1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-31 22:31 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. investigating 2026-03-31 22:46 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-03-31 23:26 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. resolved 2026-03-31 23:36 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), USA (NA1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-04 23:59 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. resolved 2026-03-05 00:53 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-13 23:08 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. investigating 2026-02-14 00:41 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-02-14 01:32 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

4. resolved 2026-02-14 01:49 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Germany (EU1), Germany (EU1), Germany (EU1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-12 22:30 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. monitoring 2026-02-13 00:36 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

3. monitoring 2026-02-13 01:06 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

4. resolved 2026-02-13 03:01 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Germany (EU1), Germany (EU1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-03 17:41 UTC

   We are aware of dashboard accessibility issues impacting visibility around AI SIEM and Event Search. We are actively investigating the root cause and working to restore normal operations.

2. identified 2026-02-03 18:20 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. monitoring 2026-02-03 19:13 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. monitoring 2026-02-03 20:28 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-02-03 20:53 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), USA (NA4), USA (NA4), Canada (NA3), Canada (NA3), Germany (EU1), Germany (EU1), Germany (EU2), Germany (EU2), Australia (AP2), Australia (AP2), India (AP3), India (AP3)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-02-02 17:10 UTC

   SentinelOne is monitoring a global false positive event caused by a third-party reputation feed misclassification of a benign file artifact. This resulted in elevated reputation-based detections, alert activity across multiple regions, and, for some customers, network...

2. monitoring 2026-02-02 20:21 UTC

   SentinelOne has mitigated the third-party reputation misclassification of hash e89cb8f5b2a05b00e85a1f549b0d1e48d148ccbf. We have manually updated our global reputation feed and issued a fleet-wide allowlist to prevent further detections. While infrastructure remains healthy,...

3. resolved 2026-02-02 21:00 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-01-29 18:08 UTC

   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.

2. monitoring 2026-01-29 19:56 UTC

   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.

3. resolved 2026-01-29 21:15 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-27 20:58 UTC

   We are aware of outages impacting multiple management consoles. Our team is actively working to restore services and will provide an update once access is fully restored. Endpoint protection remains intact during this period.

2. identified 2026-01-27 21:24 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. identified 2026-01-27 21:27 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

4. resolved 2026-01-27 21:48 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), USA (NA1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 08:00 UTC

   We are currently investigating the issue.

2. identified 2026-01-20 09:21 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-01-20 09:31 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. resolved 2026-01-20 09:56 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Germany (EU1)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-15 22:38 UTC

   We are aware of issues affecting customers ability to log into consoles in the EU1 region and are actively investigating the root cause. We apologize for the inconvenience and appreciate your patience as we work to resolve the issue.

2. resolved 2025-12-15 23:21 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-12 18:03 UTC

   Some customers may be experiencing slower than normal performance when accessing OpsCenter within the management console. We are investigating the cause of this degradation and working to restore full performance as quickly as possible. Thank you for your patience.

2. resolved 2025-12-12 19:19 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-04 08:30 UTC

   Some customers may be experiencing slower than normal performance when accessing the management console. We are investigating the cause of this degradation and working to restore full performance as quickly as possible. Thank you for your patience.

2. investigating 2025-12-04 08:31 UTC

   We are continuing to investigate this issue.

3. investigating 2025-12-04 09:30 UTC

   We are continuing to investigate this issue.

4. identified 2025-12-04 09:39 UTC

   The issue has been identified and a fix is being implemented.

5. monitoring 2025-12-04 10:01 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

6. resolved 2025-12-04 10:32 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-11-10 00:00 UTC

   We’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 have been temporarily limited.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), USA (NA1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-06 18:10 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Additionally, SentinelOne MDR services are impacted, with delayed...

2. resolved 2025-11-06 19:03 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), USA (NA1), USA (NA1), USA (NA1), USA (NA1)

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-02 16:01 UTC

   Console access is temporarily unavailable due to scheduled upgrade activities. We are working to complete maintenance as quickly as possible and will notify you once services are restored. Endpoint protection capabilities remain unaffected.

2. investigating 2025-11-02 17:02 UTC

   We are aware of the ongoing service interruption triggered from the previously scheduled maintenance activities and are actively working to resolve the issue. We apologize for the inconvenience and appreciate your patience as we work to resolve the issue. Endpoint protection...

3. investigating 2025-11-02 17:44 UTC

   We are aware of the ongoing service interruption triggered from the previously scheduled maintenance activities and are actively working to resolve the issue. Additionally, SentinelOne MDR services are impacted, with delayed investigation and response to alerts for customers in...

4. monitoring 2025-11-02 18:38 UTC

   A mitigation to restore services has been applied. We are closely monitoring system performance to ensure stability. While data ingestion has resumed, there is a temporary backlog of data still being processed. As systems catch up, you may see a surge in delayed alerts. This is...

5. resolved 2025-11-02 20:59 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Australia (AP2), Australia (AP2)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-26 01:31 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. monitoring 2025-10-26 02:04 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

3. resolved 2025-10-26 02:38 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), USA (NA1), USA (NA1), USA (NA1), USA (NA1)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 09:55 UTC

   We are aware of widespread service interruption affecting SentinelOne customers due to an AWS outage impacting many companies and cloud service providers. At this time, customer endpoints are still protected, and threat reporting is delayed, not lost. Managed response services...

2. identified 2025-10-20 10:34 UTC

   As AWS is beginning to restore services, our engineering teams are working through the backlog. Data ingestion may be delayed at this time. Customers may experience a surge in alerts as services come back online. We will provide updates as we make progress, and appreciate your...

3. identified 2025-10-20 10:59 UTC

   We are continuing to work on a fix for this issue.

4. identified 2025-10-20 11:29 UTC

   Console access has been restored. Our engineering teams are still working through the data ingestion backlog. Customers may continue to experience a surge in alerts at this time.

5. monitoring 2025-10-20 12:25 UTC

   Services have been restored, and we are working to validate the health of your systems. While data ingestion has resumed, there is still a temporary backlog of data being processed. As systems catch up, you may see a surge in delayed alerts. This is expected behavior and does...

6. identified 2025-10-20 16:07 UTC

   Due to ongoing and additional issues within AWS, our engineering teams are now investigating additional impact to customer consoles and data ingestion. We are attempting to rapidly resolve the issue and will continue to update you.

7. identified 2025-10-20 18:25 UTC

   Due to ongoing AWS issues, threat data is still delayed but securely queued—not lost. We keep working to restore full functionality.

8. monitoring 2025-10-20 20:32 UTC

   Services are being restored, and we are working to validate the health of your systems. While data ingestion has resumed, there is a backlog of data still being processed. As systems catch up, you can expect a surge in delayed alerts. We will continue to update you as we work to...

9. monitoring 2025-10-20 21:28 UTC

   We continue working to validate the health of your systems. Data ingestion has resumed and we expect the vast majority of our backlog ingestion to be completed by 4:00 a.m. UTC. We will continue to provide updates as necessary.

10. monitoring 2025-10-21 03:36 UTC

    We continue working to validate the health of your systems. Data ingestion remains in progress without issue, and the majority of our backlogs has now been ingested. Further updates will be provided as necessary.

11. resolved 2025-10-21 13:16 UTC

    All services have been fully restored following the recent AWS outage, and all delayed data has now been processed. Your security insights are up to date, and we appreciate your patience as we worked to resolve this issue and ensure continued protection.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Germany (EU1), Germany (EU1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-08 10:24 UTC

   We are aware of in issue in the EU1 region that is impacting Endpoint Data Ingestion. Customers may see delays in the availability of Endpoint data in Ops Center. Engineering is currently investigating a fix.

2. identified 2025-10-08 12:10 UTC

   Our engineering teams have identified a fix and are actively working to implement it. We will provide updates as we make progress, and appreciate your continued patience as we resolve the incident.

3. resolved 2025-10-08 15:15 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-09 17:27 UTC

   We are currently investigating an issue affecting both search and ingestion functionality on app.scalyr.com

2. investigating 2025-09-09 17:27 UTC

   We are continuing to investigate this issue.

3. identified 2025-09-09 17:57 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

4. resolved 2025-09-09 20:23 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), Germany (EU1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-08-21 17:57 UTC

   We are aware of reports of Internal Server Errors impacting some tabs in the Singularity Operations Center (SOC) regarding Cloud Native Security. The underlying issue has been identified, and our engineering teams are actively working to implement a fix. We will provide updates...

2. identified 2025-08-21 18:48 UTC

   We are aware of reports of Internal Server Errors impacting some tabs in the Singularity Operations Center (SOC) regarding Vulnerability and Misconfiguration findings. The underlying issue has been identified, and our engineering teams are actively working to implement a fix. We...

3. identified 2025-08-21 20:57 UTC

   We are continuing to work on a fix for this issue. EU1 has also been identified as an impacted region.

4. identified 2025-08-22 02:34 UTC

   We are continuing to work on a fix for this issue.

5. resolved 2025-08-22 02:59 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-14 04:01 UTC

   We are aware of delays in data ingestion impacting EDR data for some customers. You may experience a delay in the appearance of new security event data within your console. Our engineering team is investigating and working to restore normal data flow.

2. monitoring 2025-08-14 04:28 UTC

   Services have been restored, and we are monitoring EDR data ingestion to ensure there is no ongoing customer impact. While EDR data ingestion has resumed, there is a temporary backlog of data still being processed. As systems catch up, you may see a surge in delayed alerts. This...

3. resolved 2025-08-15 13:30 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), Germany (EU1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-13 15:46 UTC

   We are aware of a service interruption impacting multiple management consoles. Our team is actively working to restore services and will provide an update once access is fully restored.

2. identified 2025-08-13 16:08 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. monitoring 2025-08-13 17:28 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. monitoring 2025-08-13 18:09 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

5. resolved 2025-08-13 18:43 UTC

   Services have been restored, and we are continuing to validate the health of your systems. Data ingestion has resumed, and any residual lag should be resolved shortly.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), Germany (EU1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-11 13:11 UTC

   We are aware of delays impacting the availability of alerts in the Singularity Operations Center. Our teams are investigating the issue. We understand the importance of these alerts and are working urgently to resolve this as quickly as possible. Customers can still access these...

2. identified 2025-08-11 13:49 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. monitoring 2025-08-11 14:12 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. monitoring 2025-08-11 14:35 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-08-11 15:18 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), Germany (EU1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-11 08:46 UTC

   We are aware of outages impacting multiple management consoles. Our team is actively working to restore services and will provide an update once access is fully restored. Endpoint protection remains intact during this period.

2. identified 2025-08-11 09:14 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2025-08-11 09:14 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

4. identified 2025-08-11 09:14 UTC

   We are continuing to work on a fix for this issue.

5. monitoring 2025-08-11 09:21 UTC

   A fix has been implemented and we are monitoring the results.

6. monitoring 2025-08-11 09:21 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2025-08-11 09:22 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

8. resolved 2025-08-11 11:05 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-10 13:56 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. identified 2025-08-10 15:02 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. resolved 2025-08-10 15:45 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Germany (EU2)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-07 19:38 UTC

   We are aware of delays impacting the availability of EDR Alerts information in the Singularity Operations Center. Our teams are investigating the issue. We understand the importance of access and are working urgently to resolve this as quickly as possible. Customers can still...

2. identified 2025-08-07 20:16 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. resolved 2025-08-07 21:13 UTC

   Services 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 surge in delayed alerts. This is expected behavior and does...

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Singapore (AP1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-06 04:45 UTC

   We are aware of outages impacting multiple management consoles. Our team is actively working to restore services and will provide an update once access is fully restored. Endpoint protection remains intact during this period.

2. monitoring 2025-08-06 05:15 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

3. resolved 2025-08-06 07:29 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Canada (NA3)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-05 17:54 UTC

   We are aware of delays in data ingestion impacting some customers. You may experience a delay in the appearance of new data within your console, including security event data, asset inventories, or alerts. Our engineering team is investigating and working to restore normal data...

2. resolved 2025-08-05 18:30 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-05 17:44 UTC

   Some customers may be experiencing slower than normal performance when accessing the management console. We are investigating the cause of this degradation and working to restore full performance as quickly as possible. Thank you for your patience.

2. investigating 2025-08-05 17:51 UTC

   We are aware that some customers are experiencing some search timeout errors related to degraded search performance. Our engineering team is actively investigating and working to restore normal functionality.

3. identified 2025-08-05 18:27 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

4. monitoring 2025-08-05 18:37 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

5. monitoring 2025-08-05 18:57 UTC

   We are continuing to monitor for any further issues.

6. resolved 2025-08-05 18:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1)

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-05 11:21 UTC

   Some customers may be experiencing slower than normal performance when accessing the management console. We are investigating the cause of this degradation and working to restore full performance as quickly as possible. Thank you for your patience.

2. investigating 2025-08-05 14:51 UTC

   We briefly interrupted the connection between one console and the agent as a mitigation step. All agent console connections on this console should now be restored. Thank you for your continued patience as we work through remediation.

3. monitoring 2025-08-05 15:14 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. identified 2025-08-05 17:22 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

5. monitoring 2025-08-05 18:12 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

6. resolved 2025-08-05 18:40 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA4), Canada (NA3), Germany (EU1), Germany (EU2), Singapore (AP1), Australia (AP2), India (AP3)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-03 21:26 UTC

   Some customers may be experiencing slower than normal performance when accessing the management console. We are investigating the cause of this degradation and working to restore full performance as quickly as possible. Thank you for your patience.

2. identified 2025-08-03 22:39 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. monitoring 2025-08-04 00:40 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. resolved 2025-08-04 00:45 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: USA (NA1), USA (NA1), Germany (EU1), Germany (EU1), Singapore (AP1), Singapore (AP1), India (AP3), India (AP3)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-03 17:34 UTC

   We are aware of the ongoing service interruption and are actively investigating the root cause. We apologize for the inconvenience and appreciate your patience as we work to resolve the issue.

2. investigating 2025-08-03 18:58 UTC

   We are continuing to investigate this issue.

3. investigating 2025-08-03 18:59 UTC

   For Identity customers, as a result of intermittent connectivity issues to the licensing service, customers may be limited in their ability to configure Identity features. We are continuing to investigate this incident. Please note, endpoints continue to be protected by the...

4. investigating 2025-08-03 19:01 UTC

   We are continuing to investigate this issue.

5. investigating 2025-08-03 19:02 UTC

   We are continuing to investigate this issue.

6. identified 2025-08-03 19:23 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

7. identified 2025-08-03 19:35 UTC

   We are continuing to work on a fix for this issue.

8. identified 2025-08-03 21:11 UTC

   We have identified additional regions that may have been impacted by this incident: AP3 and EU1. Some customers in these regions may not have access to Singularity Identity detection and response features (IDR). We are continuing to investigate this issue.

9. resolved 2025-08-03 22:04 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.

Affected: Germany (EU1)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-31 17:01 UTC

   We are aware of an issue in EU1 impacting the ability of our customers to execute queries. You may experience slow query execution times or see errors returned in response to your queries. Our engineering team is investigating and working to resolve the issue.

2. identified 2025-07-31 17:41 UTC

   The underlying issue has been identified and our engineering teams are actively working to implement a fix. We will provide updates as we make progress and appreciate your continued patience as we resolve the incident.

3. monitoring 2025-07-31 19:03 UTC

   A fix has been applied and we are closely monitoring system performance to ensure stability. We will continue to observe for any further issues and will keep you updated on progress.

4. resolved 2025-07-31 20:35 UTC

   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.

Excerpts are shortened. Read the full incident on SentinelOne's status page.