**Summary**
Intermittent issues in Google SecOps with Public Preview PDF and PNG scheduled dashboard reports across multiple regions.
**Description**
The issue with Google SecOps has been resolved for all affected projects as of Friday, 2026-11-13 11:30 PST.
We thank you for your patience while we worked on resolving the issue.
**Customer Symptoms**
Customers with scheduled dashboard reports configured to generate PDF or PNG output in Google SecOps saw report generation fail or timeout.
**Workaround**
Not Applicable.
**Summary**
[Resolved] Google SecOps may have experienced an issue with Public Preview PDF and PNG scheduled dashboard reports across multiple regions.
**Description**
The issue with Google SecOps has been resolved for all affected users as of Thursday, 2026-11-12 23:40 US/Pacific.
We thank you for your patience while we worked on resolving the issue.
**Customer Symptoms**
Customers may have experienced failures or timeouts when generating or delivering scheduled dashboard reports in PDF and PNG formats. This is a Public Preview feature.
Interactive dashboards in the Google SecOps UI, underlying security data, and scheduled dashboard reports configured in CSV format were not impacted and continue to operate normally.
**Workaround**
None, as the issue is resolved.
**Description**
The issue with Google SecOps has been resolved for all affected users as of Wednesday, 2026-11-11 22:30 PST.
From our analysis, the issue was triggered by a physical disruption to network infrastructure managed by a third-party vendor. This damage temporarily reduced available network transit capacity between several regions, leading to the elevated latencies and errors observed.
Our engineering team mitigated the impact by dynamically routing around the affected network paths and prioritizing critical traffic to restore service.
We thank you for your patience while we worked on resolving the issue.
**Diagnosis / Customer Symptoms**
Customers performing searches may have observed elevated latencies and intermittent retriable errors.
**Workaround**
None at this time as the issue stands resolved.
**Summary**
Google SecOps customers may have experienced delays in normalization.
**Description**
The issue with Google SecOps has been resolved for all affected users as of Saturday, 2026-11-07 20:01 US/Pacific.
From preliminary analysis, we have identified that the issue was triggered by an internal network disruption in one of our US regions that degraded database performance and caused data indexing timeouts.
This created a backlog that delayed the availability of new data in customer searches and dashboards.
Our engineers mitigated the issue by isolating the degraded network components and scaling up compute resources in unaffected regions to successfully resume data ingestion and normalization.
We thank you for your patience while we worked on resolving the issue.
**Symptoms**
Google SecOps customers may have experienced delays in normalization.
**Summary**
Google SecOps experienced latency in several services in the US region.
**Description**
The issue with Google SecOps has been resolved for all affected users as of Friday, 2026-11-06 11:40 PST.
We thank you for your patience while we worked on resolving the issue.
**Symptoms**
Impacted customers utilizing Google SecOps may have observed latency in Search, Detections and Dashboards in the US region.
**Workaround**
None at this time.
**Summary**
The issue with elevated search error rates in Google SecOps in the asia-southeast1 (Singapore) region has been resolved.
**Description**
The issue with Google SecOps log search and query capabilities in the asia-southeast1 (Singapore) region has been resolved for all affected customers as of Tuesday, 2026-11-03 22:29 PST.
During the disruption, which began at 21:31 PST (05:31 UTC), customers in the asia-southeast1 region may have experienced intermittent errors when executing log searches or investigating alerts. Our engineering team mitigated the issue by routing search traffic away from the affected infrastructure, and search operations have returned to normal.
If you continue to experience any issues, please reach out to Google Cloud Support.
We thank you for your patience while we worked on resolving the issue.
**Customer Symptoms**
Elevated error rates affected log search and query execution in the asia-southeast1 region between 21:31 PST and 22:29 PST.
**Workaround**
None required. Normal search functionality has been fully restored.
**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
**Description**
The issue with Google SecOps has been resolved for all affected customers as of Wednesday, 2026-10-28 10:28 PDT.
We thank you for your patience as we worked to resolve this issue.
**Customer Symptoms**
Google SecOps customers in the impacted regions may have been unable to create or edit data feeds.
**Workaround**
The issue is resolved.
**Summary :** Google SecOps SIEM: Log ingestion failures for HTTPS Push feeds using custom log types
**Description :**
Our engineering team has implemented a mitigation for the Google Security Operations (SecOps) SIEM issue as of Wednesday, 2026-10-28 16:00 US/Pacific.
All new incoming traffic is now processing normally, and all the backlog of the historical data that was delayed during the incident has been processed successfully as of Thursday, 2026-10-29 13:30 US/Pacific
The issue was triggered by a recent software release that caused validation errors for custom log types on HTTPS Push feeds, which our engineering team mitigated by rolling back the update to a previous stable version and reprocessing the queued data backlog.
**Customer Symptoms :**
Google Security Operations (SecOps) Security Information and Event Management (SIEM) all customers globally experienced log ingestion failures for custom log types sent to HTTPS Push feeds.
**Description**
The issue with Google SecOps in the EU multi-region causing delays in data normalization has been resolved as of Monday, 2026-10-26 08:10 PDT.
We thank you for your patience while we worked to mitigate this issue.
**Symptoms**
In the EU multi-region, Google SecOps customers may have experienced delays in log normalization into the Unified Data Model (UDM), search and delayed execution of detection rules.
**Workaround**
The issue is mitigated.
Duration: 3h 1mWarsawFinlandBelgium+6
Google SecOps
Incident community checkThis incident
10 incidents visible (ongoing and monitoring). A free account unlocks resolved history and filters.