Who is down right now

SentinelOne · SecurityFeb 2, 2026, 17:10 UTC 8 months ago

Elevated False Positive Alert Activity

MinorDependencyUpdated 9h ago
Feb 2, 17:10 UTCFeb 2, 21:00 UTC
Duration
3h 50m
Impact
Minor
Root cause
Dependency
SentinelOne, 90 days
0 incidents
Affected
USA (NA1)USA (NA4)Canada (NA3)Germany (EU1)Germany (EU2)Australia (AP2)India (AP3)Singularity Threat Services - USA (NA1)Singularity Threat Services - USA (NA4)Singularity Threat Services - Canada (NA3)Singularity Threat Services - Germany (EU1)Singularity Threat Services - Germany (EU2)Singularity Threat Services - Australia (AP2)Singularity Threat Services - India (AP3)
Status page

Final update

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.

Timeline

  1. Resolved · Feb 2, 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.
  2. Monitoring · Feb 2, 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, 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. Monitoring · Feb 2, 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 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.

More from SentinelOne

Full history

Also caused by third-party dependency

All