Google Security Products Status Dashboard
Incident affecting Google SecOps
SecOps customers are experiencing delays in data freshness for Stats Search in multiple regions.
Incident began at 2026-07-31 10:11 and ended at 2026-08-01 22:53 (all times are US/Pacific).
Previously affected location(s)
Johannesburg (africa-south1)Taiwan (asia-east1)Tokyo (asia-northeast1)Seoul (asia-northeast3)Mumbai (asia-south1)Singapore (asia-southeast1)Sydney (australia-southeast1)Multi-region: europeWarsaw (europe-central2)Turin (europe-west12)London (europe-west2)Frankfurt (europe-west3)Zurich (europe-west6)Paris (europe-west9)Doha (me-central1)Dammam (me-central2)Tel Aviv (me-west1)Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Multi-region: us
| Date | Time | Description | |
|---|---|---|---|
| | 1 Aug 2026 | 23:10 PDT | Summary [Resolved] Google SecOps customers may have experienced delays in data freshness for Search, Stats Search, and Rule re-evaluation in multiple regions. Description The issue with Google SecOps has been resolved for all affected users as of Saturday, 2026-08-01 22:53 PDT. We thank you for your patience while we worked on resolving the issue. Symptoms Affected customers might have observed some data older than 24 hours missing, as well as incomplete Search results for some of these hours older than the last 24 hours, and rule re-evaluation may not have taken place for data ingested for those hours. Workaround None at this time as the issue stands resolved. |
| | 1 Aug 2026 | 20:42 PDT | Summary Google SecOps customers may experience delays in data freshness for Search, Stats Search, and Rule re-evaluation in multiple regions. Description Google SecOps customers are experiencing delays in data freshness for Search, Stats Search, and Rule re-evaluation which began on Friday, 2026-07-31 10:11 PDT. The issue is mitigated for most of the regions. Mitigation work is currently underway by our engineering team in Multi Region-us. We do not have an ETA for mitigation at this point. We will provide more information by Sunday, 2026-08-02 3:00 PDT. Symptoms Affected customers might see some data older than 24 hours missing, as well as incomplete Search results for some of these hours older than last 24 hours, and rule re-evaluation may not take place for data ingested for those hours. Workaround None at this time. |
| | 1 Aug 2026 | 16:38 PDT | Summary Google SecOps customers may experience delays in data freshness for Search, Stats Search, and Rule re-evaluation in multiple regions. Description Google SecOps customers are experiencing delays in data freshness for Search, Stats Search, and Rule re-evaluation which began on Friday, 2026-07-31 10:11 PDT. The issue is mitigated for most of the regions. Mitigation work is currently underway by our engineering team in Multi Region-us. We do not have an ETA for mitigation at this point. We will provide more information by Saturday, 2026-08-01 21:00 PDT. Symptoms Affected customers might see some data older than 24 hours missing, as well as incomplete Search results for some of these hours older than last 24 hours, and rule re-evaluation may not take place for data ingested for those hours. Workaround None at this time. |
| | 1 Aug 2026 | 09:07 PDT | Summary Google SecOps customers may experience delays in data freshness for Search, Stats Search, and Rule re-evaluation in multiple regions. Description Google SecOps customers are experiencing delays in data freshness for Search, Stats Search, and Rule re-evaluation which began on Friday, 2026-07-31 10:11 PDT. The issue is mitigated for most of the regions. Mitigation work is currently underway by our engineering team in Multi Region-us, Multi Region-eu and europe-west3. We do not have an ETA for mitigation at this point. We will provide more information by Saturday, 2026-08-01 16:00 PDT Symptoms Affected customers may observe inconsistent analytical and aggregate results for approximately the last 24 hours of ingested data in Stats Search, as well as incomplete Search results over the last 24 hours, and rule re-evaluation may not take place for data ingested in the last 24 hours. Workaround None at this time. |
| | 31 Jul 2026 | 21:59 PDT | Summary Google SecOps customers may experience delays in data freshness for Search, Stats Search, and Rule re-evaluation in multiple regions. Description Google SecOps customers are experiencing delays in data freshness for Search, Stats Search, and Rule re-evaluation which began on Friday, 2026-07-31 10:11 PDT. The issue is mitigated for most of the regions. Mitigation work is currently underway by our engineering team in Multi Region-us,asia-south1,asia-southeast1,australia-southeast1, Multi Region-eu,europe-west3,me-west1 and northamerica-northeast2. We do not have an ETA for mitigation at this point. We will provide more information by Saturday, 2026-08-01 10:30 PDT. We thank you for your patience while we resolve the issue. Symptoms Affected customers may observe inconsistent analytical and aggregate results for approximately the last 24 hours of ingested data in Stats Search, as well as incomplete Search results over the last 24 hours, and rule re-evaluation may not take place for data ingested in the last 24 hours. Workaround None at this time. |
| | 31 Jul 2026 | 17:02 PDT | Summary SecOps customers are experiencing delays in data freshness for Search, Stats Search, and Rules Reevaluation in multiple regions. Description Google SecOps customers are experiencing delays in data freshness for Search, Stats Search, and Rule re-evaluation which began on Friday, 2026-07-31 10:11 PDT. Our engineering team is actively investigating and implementing a mitigation. A mitigation ETA is not available at this time. We will provide an update by Friday, 2026-07-31 22:00 PDT with details. We thank you for your patience while we resolve the issue. Symptoms Affected customers will see inconsistent analytical and aggregate results for approximately the last 24 hours of ingested data in Stats Search, as well as incomplete Search results over the last 24 hours, and rule re-evaluation may not take place for data ingested in the last 24 hours. Workaround None at this time. |
| | 31 Jul 2026 | 15:57 PDT | Description Google SecOps customers are experiencing delays in data freshness for Stats Search which began on Friday, 2026-07-31 10:11 PDT. Our engineering team is actively investigating and implementing a mitigation. A mitigation ETA is not available at this time. We will provide an update by Friday, 2026-07-31 17:30 PDT with details. We thank you for your patience while we resolve the issue. Symptoms Affected customers will see inconsistent analytical and aggregate results for approximately the last 20 hours of ingested data in Stats Search. Workaround None at this time. |
| | 31 Jul 2026 | 12:44 PDT | Description Google SecOps customers are experiencing delays in data freshness for Stats Search, which began on Friday, 2026-07-31 10:11 PDT. Our engineering team is actively investigating and implementing a mitigation. A mitigation ETA is not available at this time. We will provide an update by Friday, 2026-07-31 16:00 PDT with details. We thank you for your patience while we resolve the issue. Symptoms Affected customers will see inconsistent analytical and aggregate results for approximately the last 20 hours of ingested data in Stats Search. Workaround None at this time. |
| | 31 Jul 2026 | 11:04 PDT | Description We are experiencing a Google SecOps issue, beginning on Friday, 2026-07-31 10:11 PDT. The root cause of the issue is under investigation. There is no action required by customers. Stats data will be refreshed by the engineering team once the issue is resolved. We will provide an update by Friday, 2026-07-31 12:45 PDT with details. We thank you for your patience while we worked on resolving the issue. Symptoms Delays in data availability for stats search for customers with SecOps tenants in multiple European and asia-southeast1 regions. Workaround None at this time. |
| | 31 Jul 2026 | 10:49 PDT | Description We will provide more information by Friday, 2026-07-31 11:10 PDT. Symptoms We are investigating a potential issue with Google SecOps. Workaround None at this time. |
- All times are US/Pacific