Google Security Products Status Dashboard
Incident affecting Google SecOps
Google SecOps customers are experiencing UDM (Unified Data Model) search errors
Incident began at 2025-07-03 07:28 and ended at 2025-07-03 09:35 (all times are US/Pacific).
Previously affected location(s)
Johannesburg (africa-south1)Tokyo (asia-northeast1)Mumbai (asia-south1)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Multi-region: europeTurin (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 | |
---|---|---|---|
| 3 Jul 2025 | 09:54 PDT | The issue with Google SecOps has been resolved for all affected projects as of Thursday, 2025-07-03 09:35 PDT. From our preliminary analysis, the impact was caused due to an inadvertent change resulting in an incorrect dependency for the search query engine. Our engineering team mitigated the impact by removing that dependency We thank you for your patience while we worked on resolving the issue. |
| 3 Jul 2025 | 09:35 PDT | Description : Mitigation work is currently underway by our engineering team and has been completed for the following regions :
We are continuing to apply the mitigation for the remaining impacted regions. The mitigation is expected to be completed by Thursday, 2025-07-03 09:45 PDT. We will provide more information by Thursday, 2025-07-03 10:00 PDT. Customer Symptoms : Customers may experience errors stating “Search has encountered and error and could not load data” Workaround : None at this time |
| 3 Jul 2025 | 09:02 PDT | Description : We are experiencing an issue with Google SecOps beginning on Thursday, 2025-07-03 07:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2025-07-03 10:00 PDT with current details. Customer Symptoms : Customers may experience errors stating “Search has encountered and error and could not load data” Workaround : None at this time |
- All times are US/Pacific