Incident details | Google Security Products Status Dashboard

Google Security Products Status Dashboard
Incidents
Investigating elevated latency and errors with Google Secops.

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

Investigating elevated latency and errors with Google Secops.

Incident began at 2026-10-14 12:05 and ended at 2026-10-14 14:06 (all times are US/Pacific).

Previously affected location(s)

Sydney (australia-southeast1)Tel Aviv (me-west1)

Date	Time	Description
14 Oct 2026	14:23 PDT	Summary Mitigated elevated latency and errors with Google Secops. Description The issue with Google Security Operations (SIEM) in the `australia-southeast1` and `me-west1` regions has been resolved for all affected customers as of Wednesday, 2026-10-14 14:06 US/Pacific. Between Wednesday, 2026-10-14 12:05 US/Pacific and 14:06 US/Pacific, customers in `australia-southeast1` and `me-west1` experienced elevated log ingestion errors and delays in log normalization and detections. Additionally, customers in both regions experienced errors when accessing Search (UI and API) and Dashboards from 12:05 US/Pacific until 13:25 US/Pacific. Customer Action Required for Direct Ingestion API Users: • Ingestion: Customers sending logs without automated retry logic should resubmit any log data that received error responses during the impact window (12:05 to 14:06 US/Pacific). • Managed Forwarders & Agents: Customers ingesting logs via the Google SecOps forwarder or the Bindplane agent do not need to take action; buffered logs are retried and processed automatically. A database configuration change caused elevated transaction timeouts across the ingestion and indexing pipelines in the affected regions. The Product Engineering Team detected the issue, rolled back the configuration change, and scaled processing capacity to clear the backlog. We thank you for your patience while we worked on resolving this issue. Symptoms Customers in `australia-southeast1` and `me-west1` experienced HTTP/RPC errors when ingesting logs, as well as delays in log normalization and rule detections. Customers also experienced errors loading Dashboards and running queries in Search (UI and API) until 13:25 US/Pacific. Workaround None required as the issue is mitigated. Customers using the direct Chronicle Ingestion API without client-side retries should resubmit any logs that returned errors between 12:05 and 14:06 US/Pacific.
14 Oct 2026	13:33 PDT	Description: Our engineering team is actively working on mitigating the ingestion issues. As of 13:25 PDT, the errors for Google SecOps Search (both UI and API) and Dashboards are resolved. We do not have an ETA for ingestion mitigation at this point. We will provide more information by Wednesday, 2026-10-14 14:30 PDT. Symptoms: Google SecOps customers are experiencing elevated latency with Ingestion and Detections. Errors occurred for users of SecOps Search (UI and API) and Dashboards until 13:25 PDT. Workaround: None at this time.
14 Oct 2026	13:15 PDT	Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2026-10-14 14:15 PDT. Symptoms: Googler SecOps customers are experiencing elevated latency with Ingestion and Detections. Errors may occur for users of SecOps Search (UI and API) and Dashboards. Workaround: None at this time.
14 Oct 2026	13:06 PDT	Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2026-10-14 14:15 PDT. Symptoms: Customers are experiencing elevated latency and errors with Google Secops search, ingestion , detections, agents, dashboards, and datatables. Workaround: None at this time.
14 Oct 2026	12:57 PDT	Description: We are experiencing an issue with Google SecOps beginning at Wednesday, 2026-10-14 12:05 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-10-14 14:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Customers are experiencing elevated latency and errors with Google Secops search, ingestion , detections, agents, dashboards, and datatables. Workaround: None at this time.

All times are US/Pacific