Google Security Products Status Dashboard
-
Available -
Service information -
Service disruption -
Service outage
Incident affecting Google SecOps
[Informational] Google SecOps customers are experiencing staleness with Entity Context Graph (ECG) "first seen" and "last seen" timestamps. Only “Domain”, “file hash” and “IP address” identifiers are impacted at this time.
Incident began at 2026-01-15 00:00 (all times are US/Pacific).
Currently affected location(s)
Johannesburg (africa-south1)Tokyo (asia-northeast1)Mumbai (asia-south1)Singapore (asia-southeast1)Jakarta (asia-southeast2)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 | |
|---|---|---|---|
| | 12 Feb 2026 | 13:12 PST | We are experiencing an issue with Google SecOps, beginning on Thursday, 2026-01-15. Mitigation work is ongoing and the mitigation is expected to complete by Friday, 2026-02-20. The staleness with search and display results of “first seen” and “last seen” timestamps for entities is now resolved in asia-northeast1, asia-south1, europe-west3, europe-west6, northamerica-northeast2, southamerica-east1. We will provide more information by Tuesday, 2026-02-17 12:00 US/Pacific with current details. Customer Symptoms
Workaround None at this time. |
| | 12 Feb 2026 | 12:22 PST | We are experiencing an issue with Google SecOps, beginning on Thursday, 2026-01-15. Mitigation work is currently underway by our engineering team. We will provide more information by Thursday, 2026-02-12 16:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Customer Symptoms
Workaround None at this time. |
| | 11 Feb 2026 | 11:03 PST | We are experiencing an issue with Google SecOps, beginning on Thursday, 2026-01-15. Mitigation work is currently underway by our engineering team. We will provide more information by Thursday, 2026-02-12 12:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Customer Symptoms
Workaround None at this time. |
- All times are US/Pacific