SentinelOne incident

[NA1] Service Interruption due to AWS Outage

Major Resolved View vendor source →

SentinelOne experienced a major incident on October 20, 2025 affecting USA (NA1) and USA (NA1) and 1 more component, lasting 1d 3h. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 09:55 AM UTC
Resolved
Oct 21, 2025, 01:16 PM UTC
Duration
1d 3h
Detected by Pingoru
Oct 20, 2025, 09:55 AM UTC

Affected components

USA (NA1)USA (NA1)USA (NA1)USA (NA1)USA (NA1)USA (NA1)

Update timeline

  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.