SentinelOne Outage History

SentinelOne is up right now

Pingoru has recorded 39 incidents for SentinelOne: 22 in the last 12 months and 0 in the last 90 days.

Source: status.sentinelone.com

39incidents recorded
22last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking SentinelOne in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202614 of 720 (1%)
May 2026114 of 744 (2%)
June 202622 of 720 (0%)
July 2026214 of 744 (2%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 517 (0%)

Incidents, newest first

Critical July 12, 2026 [EU1, NA1] - Multiple Consoles Inaccessible 5h 21m USA (NA1), USA (NA1), USA (NA1), USA (NA1) and 8 more

Started Jul 12, 2026, 11:36 AM UTC· resolved Jul 12, 2026, 04:58 PM UTC

  1. investigating Jul 12, 2026, 11:36 AM 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 Jul 12, 2026, 12:00 PM 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 Jul 12, 2026, 02:37 PM 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 Jul 12, 2026, 04:58 PM 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.

Read the full incident report →

Minor July 6, 2026 [AP1, AP2, AP3, EU1, EU2, EU3, ME1, NA1, NA2, NA3, NA4] - Delayed Data Ingestion 8h 52m USA (NA1), USA (NA4), Canada (NA3), Germany (EU1) and 4 more

Started Jul 06, 2026, 06:58 AM UTC· resolved Jul 06, 2026, 03:50 PM UTC

  1. identified Jul 06, 2026, 06:58 AM 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 flow.

  2. identified Jul 06, 2026, 10:23 AM 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 Jul 06, 2026, 03:50 PM 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 not indicate new or ongoing threats.

Read the full incident report →

Major June 5, 2026 [AP1] - Delayed Data Ingestion 1h 28m Singapore (AP1)

Started Jun 05, 2026, 09:03 AM UTC· resolved Jun 05, 2026, 10:32 AM UTC

  1. investigating Jun 05, 2026, 09:03 AM 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 flow.

  2. investigating Jun 05, 2026, 09:27 AM 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 Jun 05, 2026, 09:37 AM 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 Jun 05, 2026, 10:32 AM 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.

Read the full incident report →

Minor June 2, 2026 [EU1] - Delayed Data Ingestion 50m Germany (EU1)

Started Jun 02, 2026, 09:43 AM UTC· resolved Jun 02, 2026, 10:33 AM UTC

  1. investigating Jun 02, 2026, 09:43 AM 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 flow.

  2. identified Jun 02, 2026, 10:08 AM UTC

    To be updated

  3. monitoring Jun 02, 2026, 10:21 AM 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 Jun 02, 2026, 10:33 AM 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.

Read the full incident report →

Notice May 8, 2026 [NA1] Service Interruption 13h 32m USA (NA1), USA (NA1), USA (NA1), USA (NA1) and 2 more

Started May 08, 2026, 02:05 AM UTC· resolved May 08, 2026, 03:38 PM UTC

  1. investigating May 08, 2026, 02:05 AM 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 May 08, 2026, 02:32 AM 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 May 08, 2026, 03:38 PM 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.

Read the full incident report →

Notice April 6, 2026 [EU1] Delayed Data Ingestion 3h 59m Germany (EU1)

Started Apr 06, 2026, 05:20 PM UTC· resolved Apr 06, 2026, 09:19 PM UTC

  1. investigating Apr 06, 2026, 05:20 PM 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 flow.

  2. investigating Apr 06, 2026, 06:40 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 06, 2026, 07:56 PM 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 not indicate new or ongoing threats.

  4. resolved Apr 06, 2026, 09:19 PM 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.

Read the full incident report →

Notice March 31, 2026 [ME1] Delayed Data Ingestion 1h 4m KSA (ME1), KSA (ME1), KSA (ME1)

Started Mar 31, 2026, 10:31 PM UTC· resolved Mar 31, 2026, 11:36 PM UTC

  1. investigating Mar 31, 2026, 10:31 PM 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 flow.

  2. investigating Mar 31, 2026, 10:46 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 31, 2026, 11:26 PM 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 Mar 31, 2026, 11:36 PM 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.

Read the full incident report →

Notice March 4, 2026 [NA1] Delayed Data Ingestion 53m USA (NA1), USA (NA1), USA (NA1)

Started Mar 04, 2026, 11:59 PM UTC· resolved Mar 05, 2026, 12:53 AM UTC

  1. investigating Mar 04, 2026, 11:59 PM 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 flow.

  2. resolved Mar 05, 2026, 12:53 AM 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.

Read the full incident report →

Notice February 3, 2026 [EU1] Partial Platform Disruption 3h 12m Germany (EU1), Germany (EU1)

Started Feb 03, 2026, 05:41 PM UTC· resolved Feb 03, 2026, 08:53 PM UTC

  1. investigating Feb 03, 2026, 05:41 PM 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 Feb 03, 2026, 06:20 PM 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 Feb 03, 2026, 07:13 PM 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 Feb 03, 2026, 08:28 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 03, 2026, 08:53 PM 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.

Read the full incident report →

Minor February 2, 2026 Elevated False Positive Alert Activity 3h 49m USA (NA1), USA (NA1), USA (NA4), USA (NA4) and 10 more

Started Feb 02, 2026, 05:10 PM UTC· resolved Feb 02, 2026, 09:00 PM UTC

  1. monitoring Feb 02, 2026, 05:10 PM 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 quarantines where enforcement policies are enabled. Mitigation actions have been implemented. Teams continue to monitor platform stability and assist customers with any remaining cleanup. Additional updates will be shared if conditions change.

  2. monitoring Feb 02, 2026, 08:21 PM 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, customers may experience temporary console performance degradation and brief false positive alerts as agents check in to receive the update. These symptoms will subside as the allowlist propagation completes. We will continue to monitor the environment for stability and provide updates should this change.

  3. resolved Feb 02, 2026, 09:00 PM 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.

Read the full incident report →

Major January 29, 2026 [NA1] Partial Service Disruption 3h 7m USA (NA1)

Started Jan 29, 2026, 06:08 PM UTC· resolved Jan 29, 2026, 09:15 PM UTC

  1. identified Jan 29, 2026, 06:08 PM 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 Jan 29, 2026, 07:56 PM 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 Jan 29, 2026, 09:15 PM 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.

Read the full incident report →

Notice January 27, 2026 NA1 Multiple Consoles Down 50m USA (NA1)

Started Jan 27, 2026, 08:58 PM UTC· resolved Jan 27, 2026, 09:48 PM UTC

  1. investigating Jan 27, 2026, 08:58 PM 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 Jan 27, 2026, 09:24 PM 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 Jan 27, 2026, 09:27 PM 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 Jan 27, 2026, 09:48 PM 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.

Read the full incident report →

Notice January 20, 2026 EventDB and SDL experiencing partial outage 1h 55m USA (NA1), USA (NA1), USA (NA1)

Started Jan 20, 2026, 08:00 AM UTC· resolved Jan 20, 2026, 09:56 AM UTC

  1. investigating Jan 20, 2026, 08:00 AM UTC

    We are currently investigating the issue.

  2. identified Jan 20, 2026, 09:21 AM UTC

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

  3. monitoring Jan 20, 2026, 09:31 AM 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 Jan 20, 2026, 09:56 AM 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.

Read the full incident report →

Minor December 15, 2025 [EU1] intermittent console log in errors 42m Germany (EU1)

Started Dec 15, 2025, 10:38 PM UTC· resolved Dec 15, 2025, 11:21 PM UTC

  1. investigating Dec 15, 2025, 10:38 PM 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 Dec 15, 2025, 11:21 PM 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.

Read the full incident report →

Minor December 12, 2025 [NA1] Degraded Performance on SOC 1h 16m USA (NA1)

Started Dec 12, 2025, 06:03 PM UTC· resolved Dec 12, 2025, 07:19 PM UTC

  1. investigating Dec 12, 2025, 06:03 PM 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 Dec 12, 2025, 07:19 PM 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.

Read the full incident report →

Major December 4, 2025 US-EAST-01 Consoles 2h 2m USA (NA1)

Started Dec 04, 2025, 08:30 AM UTC· resolved Dec 04, 2025, 10:32 AM UTC

  1. investigating Dec 04, 2025, 08:30 AM 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 Dec 04, 2025, 08:31 AM UTC

    We are continuing to investigate this issue.

  3. investigating Dec 04, 2025, 09:30 AM UTC

    We are continuing to investigate this issue.

  4. identified Dec 04, 2025, 09:39 AM UTC

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

  5. monitoring Dec 04, 2025, 10:01 AM 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 Dec 04, 2025, 10:32 AM 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.

Read the full incident report →

Notice November 9, 2025 [NA1] Console degraded performance 5h 30m

Started Nov 09, 2025, 06:30 PM UTC· resolved Nov 10, 2025, 12:00 AM UTC

  1. resolved Nov 10, 2025, 06:00 AM 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.

Read the full incident report →

Notice November 2, 2025 NA1 Degraded Performance 4h 57m USA (NA1), USA (NA1), USA (NA1), USA (NA1) and 2 more

Started Nov 02, 2025, 04:01 PM UTC· resolved Nov 02, 2025, 08:59 PM UTC

  1. investigating Nov 02, 2025, 04:01 PM 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 Nov 02, 2025, 05:02 PM 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 capabilities remain unaffected.

  3. investigating Nov 02, 2025, 05:44 PM 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 this region. The MDR team is ready to investigate and respond to alerts once this issue is resolved. We apologize for the inconvenience and appreciate your patience as we work to resolve the issue. Endpoint protection capabilities remain unaffected.

  4. monitoring Nov 02, 2025, 06:38 PM 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 expected behavior. SentinelOne MDR has begun investigating and responding to alerts that occurred during this service disruption. We will continue to observe for any further issues and will keep you updated on progress.

  5. resolved Nov 02, 2025, 08:59 PM 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.

Read the full incident report →

Minor October 26, 2025 [AP2] Delayed Data Ingestion 1h 6m Australia (AP2), Australia (AP2)

Started Oct 26, 2025, 01:31 AM UTC· resolved Oct 26, 2025, 02:38 AM UTC

  1. investigating Oct 26, 2025, 01:31 AM 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 flow.

  2. monitoring Oct 26, 2025, 02:04 AM 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 not indicate new or ongoing threats.

  3. resolved Oct 26, 2025, 02:38 AM 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.

Read the full incident report →

Major October 20, 2025 [NA1] Service Interruption due to AWS Outage 1d 3h USA (NA1), USA (NA1), USA (NA1), USA (NA1) and 2 more

Started Oct 20, 2025, 09:55 AM UTC· resolved Oct 21, 2025, 01:16 PM UTC

  1. identified Oct 20, 2025, 09:55 AM 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 will have impacted visibility. We apologize for the inconvenience and appreciate your patience as we work to resolve and mitigate the issue with AWS.

  2. identified Oct 20, 2025, 10:34 AM 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 continued patience as we resolve the incident.

  3. identified Oct 20, 2025, 10:59 AM UTC

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

  4. identified Oct 20, 2025, 11:29 AM 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 Oct 20, 2025, 12:25 PM 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 not indicate new or ongoing threats. We will continue to update you as we work to fully resolve the issue.

  6. identified Oct 20, 2025, 04:07 PM 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 Oct 20, 2025, 06:25 PM 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 Oct 20, 2025, 08:32 PM 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 fully restore services.

  9. monitoring Oct 20, 2025, 09:28 PM 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 Oct 21, 2025, 03:36 AM 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 Oct 21, 2025, 01:16 PM 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.

Read the full incident report →

Major October 8, 2025 EU1 Delayed Endpoint Data Ingestion 4h 51m Germany (EU1), Germany (EU1)

Started Oct 08, 2025, 10:24 AM UTC· resolved Oct 08, 2025, 03:15 PM UTC

  1. investigating Oct 08, 2025, 10:24 AM 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 Oct 08, 2025, 12:10 PM 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 Oct 08, 2025, 03:15 PM 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.

Read the full incident report →

Major September 9, 2025 [NA1] Dataset Service Interruption with data ingestion and search functionality 2h 56m

Started Sep 09, 2025, 05:27 PM UTC· resolved Sep 09, 2025, 08:23 PM UTC

  1. investigating Sep 09, 2025, 05:27 PM UTC

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

  2. investigating Sep 09, 2025, 05:27 PM UTC

    We are continuing to investigate this issue.

  3. identified Sep 09, 2025, 05:57 PM 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 Sep 09, 2025, 08:23 PM 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.

Read the full incident report →

Major August 21, 2025 [NA1] Issues with Vulnerability and Misconfiguration findings in the SOC 9h 1m USA (NA1), Germany (EU1)

Started Aug 21, 2025, 05:57 PM UTC· resolved Aug 22, 2025, 02:59 AM UTC

  1. identified Aug 21, 2025, 05:57 PM 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 as we make progress, and appreciate your continued patience as we resolve the incident.

  2. identified Aug 21, 2025, 06:48 PM 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 will provide updates as we make progress, and appreciate your continued patience as we resolve the incident.

  3. identified Aug 21, 2025, 08:57 PM UTC

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

  4. identified Aug 22, 2025, 02:34 AM UTC

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

  5. resolved Aug 22, 2025, 02:59 AM 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.

Read the full incident report →

Minor August 14, 2025 NA1 Delayed Ingest of EDR Data 1d 9h USA (NA1)

Started Aug 14, 2025, 04:01 AM UTC· resolved Aug 15, 2025, 01:30 PM UTC

  1. investigating Aug 14, 2025, 04:01 AM 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 Aug 14, 2025, 04:28 AM 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 is expected behavior and does not indicate new or ongoing threats.

  3. resolved Aug 15, 2025, 01:30 PM 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.

Read the full incident report →

Major August 13, 2025 [NA1, EU1] Multiple Consoles Down 2h 57m USA (NA1), USA (NA1), Germany (EU1)

Started Aug 13, 2025, 03:46 PM UTC· resolved Aug 13, 2025, 06:43 PM UTC

  1. investigating Aug 13, 2025, 03:46 PM 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 Aug 13, 2025, 04:08 PM 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 Aug 13, 2025, 05:28 PM 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 Aug 13, 2025, 06:09 PM 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 not indicate new or ongoing threats.

  5. resolved Aug 13, 2025, 06:43 PM 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.

Read the full incident report →