SentinelOne incident

[AP1, AP2, AP3, EU1, EU2, EU3, ME1, NA1, NA2, NA3, NA4] - Delayed Data Ingestion

Minor Resolved View vendor source →

SentinelOne experienced a minor incident on July 6, 2026 affecting USA (NA1) and USA (NA4) and 1 more component, lasting 8h 52m. The incident has been resolved; the full update timeline is below.

Started
Jul 06, 2026, 06:58 AM UTC
Resolved
Jul 06, 2026, 03:50 PM UTC
Duration
8h 52m
Detected by Pingoru
Jul 06, 2026, 06:58 AM UTC

Affected components

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

Update timeline

  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.