Incident details | Google Security Products Status Dashboard

Google Security Products Status Dashboard
Incidents
Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed.

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 SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed.

Incident began at 2026-08-25 05:06 and ended at 2026-09-11 22:45 (all times are US/Pacific).

Previously affected location(s)

Johannesburg (africa-south1)Taiwan (asia-east1)Tokyo (asia-northeast1)Seoul (asia-northeast3)Mumbai (asia-south1)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Multi-region: europeWarsaw (europe-central2)Finland (europe-north1)Belgium (europe-west1)Turin (europe-west12)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)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: usIowa (us-central1)South Carolina (us-east1)

Date	Time	Description
11 Sep 2026	23:08 PDT	Summary: Google SecOps customers may have experienced an issue where some of the logs chunks are stuck in the queue and are not processed. Description: The issue with Google SecOps has been resolved for all the customers as of Friday, 2026-09-11 22:45 PDT. From preliminary analysis, the issue was triggered by a recent code change and our engineering team successfully rolled out a code fix across all regions to restore the live traffic. Engineers will now continue to process all historical logs in the queue for the next 72 hours. We thank you for your patience while we worked on resolving the issue. Symptoms: Some SecOps customers may have experienced an issue with ingesting some of their log batches. This was a result of ingestion processing for specific log patterns. Workaround: None
11 Sep 2026	20:17 PDT	Summary: Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed. Description: Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed; the issue started Tuesday, 2026-08-25 05:06 PDT. Our engineering team has identified the root cause, provided a fix and the US region is currently mitigated. The fix is currently being rolled out in other regions and estimated to finish within 2-3 hours for new logs. Once the fix is rolled out completely we will process all historical logs in the queue within 72 hours after the mitigation. We will provide an update by Friday, 2026-09-11 23:30 PDT. Symptoms: Some SecOps customers may experience an issue with ingesting some of their log batches. This is a result of ingestion processing for specific log patterns. Workaround: None at this time.
11 Sep 2026	16:43 PDT	Summary: Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed. Description: Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed; the issue started Tuesday, 2026-08-25 05:06 PDT. Our engineering team has identified the root cause, provided a fix and it is currently being rolled out. We estimate the issue to be resolved within 4-6 hours across all regions for new logs. Once the fix is rolled out we will process all historical logs in the queue within 72 hours after the mitigation. We will provide an update by Friday, 2026-09-11 20:30 PDT. Symptoms: Some SecOps customers may experience an issue with ingesting some of their log batches. This is a result of ingestion processing for specific log patterns. Workaround: None at this time.

Date

Time

Description

11 Sep 2026

23:08 PDT

Summary:

Google SecOps customers may have experienced an issue where some of the logs chunks are stuck in the queue and are not processed.

Description:

The issue with Google SecOps has been resolved for all the customers as of Friday, 2026-09-11 22:45 PDT.

From preliminary analysis, the issue was triggered by a recent code change and our engineering team successfully rolled out a code fix across all regions to restore the live traffic.

Engineers will now continue to process all historical logs in the queue for the next 72 hours.

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

Symptoms:

Some SecOps customers may have experienced an issue with ingesting some of their log batches. This was a result of ingestion processing for specific log patterns.

Workaround:

None

11 Sep 2026

20:17 PDT

Summary:

Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed.

Description:

Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed; the issue started Tuesday, 2026-08-25 05:06 PDT.

Our engineering team has identified the root cause, provided a fix and the US region is currently mitigated. The fix is currently being rolled out in other regions and estimated to finish within 2-3 hours for new logs. Once the fix is rolled out completely we will process all historical logs in the queue within 72 hours after the mitigation.

We will provide an update by Friday, 2026-09-11 23:30 PDT.

Symptoms:

Some SecOps customers may experience an issue with ingesting some of their log batches. This is a result of ingestion processing for specific log patterns.

Workaround:

None at this time.

11 Sep 2026

16:43 PDT

Summary:

Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed.

Description:

Google SecOps customers may experience an issue where some of the logs chunks are stuck in the queue and are not processed; the issue started Tuesday, 2026-08-25 05:06 PDT.

Our engineering team has identified the root cause, provided a fix and it is currently being rolled out. We estimate the issue to be resolved within 4-6 hours across all regions for new logs. Once the fix is rolled out we will process all historical logs in the queue within 72 hours after the mitigation.

We will provide an update by Friday, 2026-09-11 20:30 PDT.

Symptoms:

Some SecOps customers may experience an issue with ingesting some of their log batches. This is a result of ingestion processing for specific log patterns.

Workaround:

None at this time.

All times are US/Pacific