Google Security Products Status Dashboard
Incident affecting Google SecOps
Some Google SecOps customers in the US multi-region may experience delays with data normalization and detections.
Incident began at 2026-09-13 05:50 and ended at 2026-09-13 07:30 (all times are US/Pacific).
Previously affected location(s)
Multi-region: us
| Date | Time | Description | |
|---|---|---|---|
| | 13 Sep 2026 | 08:14 PDT | Summary: Some Google SecOps customers in the US multi-region may have experienced delays with data normalization and detections. Description: The issue with Google SecOps in the US multi-region has been resolved for all affected users as of Sunday, 2026-09-13 07:30 PDT. Log ingestion remained operational throughout, all incoming data was safely queued, and no data was lost. We thank you for your patience while we worked on the resolution of the issue. Symptoms: In the US multi-region, some Google SecOps customers may have experienced delays in log normalization into the Unified Data Model (UDM) and delayed execution of detection rules. Workaround: This is the final notification. |
| | 13 Sep 2026 | 07:34 PDT | Description: We are experiencing an issue with Google SecOps in the US multi-region causing delays in data normalization and detections for some customers, starting on Sunday, 2026-09-13 5:50 PDT. Log ingestion remains operational, and ingested data is safely queued and will be processed as backlog clears. Our Product Engineering Team is actively investigating and deploying mitigations to relieve processing latency. We will provide our next update by Sunday, 2026-09-13 08:00 PDT. We apologize to all who are affected by this disruption. Symptoms: In the US multi-region, some Google SecOps customers may experience delays in log normalization into the Unified Data Model (UDM) and delayed execution of detection rules. Workaround: None at this time. Ingested log data is safely queued and will be normalized automatically without requiring customer action. |
- All times are US/Pacific