Incident details | Google Security Products Status Dashboard

Google Security Products Status Dashboard
Incidents
Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1

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

Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1

Incident began at 2026-10-15 11:22 and ended at 2026-10-15 12:10 (all times are US/Pacific).

Previously affected location(s)

Iowa (us-central1)South Carolina (us-east1)

	Date	Time	Description
	15 Oct 2026	13:02 PDT	Summary : Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1 Description : The issue with Google SecOps has been resolved for all affected projects as of Thursday, 2026-10-15 12:10 PDT. Based on our initial analysis, the incident was triggered by transient underlying network connectivity issues in the US region, which led to write contention in the backend indexing storage layer and retry queue backlogs. We mitigated the impact by isolating the high-volume traffic pattern to relieve storage contention and rolling back a recent indexing service update while the queued backlog drained. All queued events were durably retained and processed with no data loss. We thank you for your patience while we worked on resolving the issue. Symptoms Customers using Google SecOps in the US region (us-central1, us-east1) experienced elevated latency during log ingestion, normalization, and indexing. As a result, recently ingested security telemetry and events were delayed before appearing in search results, dashboards, and detections. Workaround None. Queued events have been processed and indexed.
	15 Oct 2026	12:22 PDT	Summary : Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1 Description : We are experiencing an issue with Google SecOps beginning on Thursday, 2026-10-15 11:22 PDT. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2026-10-15 12:45 PDT with current details. We apologize to all who are affected by the disruption. Symptoms Customers using Google SecOps in the US region (us-central1, us-east1) may experience elevated latency during log ingestion, normalization, and indexing. As a result, recently ingested security telemetry and events may be delayed before appearing in search results, dashboards, and detections. Workaround None at this time. Unprocessed events are queued and will be indexed as the pipeline recovers.

Date

Time

Description

15 Oct 2026

13:02 PDT

Summary : Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1

Description : The issue with Google SecOps has been resolved for all affected projects as of Thursday, 2026-10-15 12:10 PDT.

Based on our initial analysis, the incident was triggered by transient underlying network connectivity issues in the US region, which led to write contention in the backend indexing storage layer and retry queue backlogs.

We mitigated the impact by isolating the high-volume traffic pattern to relieve storage contention and rolling back a recent indexing service update while the queued backlog drained. All queued events were durably retained and processed with no data loss.

We thank you for your patience while we worked on resolving the issue.

Symptoms

Customers using Google SecOps in the US region (us-central1, us-east1) experienced elevated latency during log ingestion, normalization, and indexing. As a result, recently ingested security telemetry and events were delayed before appearing in search results, dashboards, and detections.

Workaround

None. Queued events have been processed and indexed.

15 Oct 2026

12:22 PDT

Summary : Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1

Description : We are experiencing an issue with Google SecOps beginning on Thursday, 2026-10-15 11:22 PDT.

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2026-10-15 12:45 PDT with current details.

We apologize to all who are affected by the disruption.

Symptoms

Customers using Google SecOps in the US region (us-central1, us-east1) may experience elevated latency during log ingestion, normalization, and indexing. As a result, recently ingested security telemetry and events may be delayed before appearing in search results, dashboards, and detections.

Workaround

None at this time. Unprocessed events are queued and will be indexed as the pipeline recovers.

All times are US/Pacific