Google Security Products Status Dashboard

This page provides status information on the services that are part of Google Security Products. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. For additional information on these services, please visit https://cloud.google.com/security.

Incident affecting Google SecOps

Google Security Operations (SIEM) customers using Customer-Managed Encryption Keys (CMEK) in all US regions are experiencing indexing delays on newly ingested events.

Incident began at 2026-10-29 10:21 and ended at 2026-10-29 21:35 (all times are US/Pacific).

Previously affected location(s)

Multi-region: us

Date Time Description
29 Oct 2026 21:48 PDT

Summary

Google Security Operations (SIEM) customers using Customer-Managed Encryption Keys (CMEK) in all US regions may have experienced indexing delays on newly ingested events.

Description

The issue tied to CMEK in Google Security Operations (SIEM) has been resolved for all affected customers as of Thursday, 2026-10-29 21:35 US/Pacific.

The backlog has been cleared, log ingestion is fully functional, and all ingested data has been safely processed.

The issue primarily manifested as search errors on specific query patterns. CMEK customers may see sporadic search errors for up to next 4 hours.

To resolve the issue, engineering executed a rollback of the recent changes, enabling the queued event batches to drain completely.

We thank you for your patience while we worked to mitigate this issue.

Customer Symptoms

Affected CMEK customers in all US regions may have experienced delays in newly ingested events appearing across all product features except raw log search.

Log ingestion remained operational, ingested data was safely queued, and no data has been lost.

Workaround

None

29 Oct 2026 21:29 PDT

Summary

Google Security Operations (SIEM) customers using Customer-Managed Encryption Keys (CMEK) in all US regions are experiencing indexing delays on newly ingested events.

Description

We are experiencing an issue with Google Security Operations (SIEM) beginning on Thursday, 2026-10-29 10:21 US/Pacific, affecting customers configured with Customer-Managed Encryption Keys (CMEK) in US regions. Non-CMEK customers in all US regions and customers in all other regions are not impacted.

Our engineering team has identified the root cause as a recent backend update. We are continuing with the rollback to mitigate the issue and monitor for any side effects.

We will provide our next update by Thursday, 2026-10-29 23:30 US/Pacific.

Customer Symptoms

Affected CMEK customers in all US regions may experience delays in newly ingested events appearing across all product features except raw log search.

Log ingestion remains operational, ingested data is safely queued, and no data has been lost.

Workaround

None at this time. Ingested log data is queued and will be indexed and processed once mitigation completes, without requiring customer action.

29 Oct 2026 20:25 PDT

Summary

Google Security Operations (SIEM) customers using Customer-Managed Encryption Keys (CMEK) in all US regions are experiencing indexing delays on newly ingested events.

Description

We are experiencing an issue with Google Security Operations (SIEM) beginning on Thursday, 2026-10-29 10:21 US/Pacific, affecting customers configured with Customer-Managed Encryption Keys (CMEK) in US regions. Non-CMEK customers in all US regions and customers in all other regions are not impacted.

Our engineering team has identified the root cause as a recent backend update and is actively working on a rollback to mitigate the issue.

We will provide our next update by Thursday, 2026-10-29 21:30 US/Pacific.

Customer Symptoms

Affected CMEK customers in all US regions may experience delays in newly ingested events appearing across all product features except raw log search.

Log ingestion remains operational, ingested data is safely queued, and no data has been lost.

Workaround

None at this time. Ingested log data is queued and will be indexed and processed once mitigation completes, without requiring customer action.