Google Security Products Status Dashboard
Incident affecting Google SecOps
Google SecOps SIEM: Log ingestion failures for HTTPS Push feeds using custom log types
Incident began at 2026-10-27 10:32 and ended at 2026-10-29 13:30 (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 | |
|---|---|---|---|
| | 29 Oct 2026 | 13:38 PDT | 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. |
| | 29 Oct 2026 | 11:54 PDT | 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. Our team is actively working to process the backlog of historical data that was delayed during the incident. The processing of the historical data is completed for the majority of data. We will provide another update by Thursday, 2026-10-29 18:00 US/Pacific with current details on the recovery progress of the delayed logs. Customer Symptoms : Google Security Operations (SecOps) Security Information and Event Management (SIEM) all customers globally are experiencing log ingestion failures for custom log types sent to HTTPS Push feeds. Workaround : No workaround is required at this time. Data will be re-processed as the system recovers. |
| | 28 Oct 2026 | 16:09 PDT | 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) Security Information and Event Management (SIEM) issue as of Wednesday, 2026-10-28 16:00 US/Pacific. All new incoming traffic is now processing normally. Our team is actively working to process the backlog of historical data that was delayed during the incident. We will provide another update by Thursday, 2026-10-29 12:00 US/Pacific with current details on the recovery progress of the delayed logs. Customer Symptoms : Google Security Operations (SecOps) Security Information and Event Management (SIEM) all customers globally are experiencing log ingestion failures for custom log types sent to HTTPS Push feeds. Workaround : No workaround is required at this time. Data will be re-processed as the system recovers. |
| | 28 Oct 2026 | 14:27 PDT | Summary : Google SecOps SIEM: Log ingestion failures for HTTPS Push feeds using custom log types Description : We are experiencing an issue with Google SecOps beginning on Tuesday 2026-10-27 10:32 PDT (Exact time varies by region) Our engineering team is actively working on mitigation efforts. We will provide an update by Wednesday, 2026-10-28 16:30 PDT with current details. Customer Symptoms : Google Security Operations (SecOps) Security Information and Event Management (SIEM) all customers globally are experiencing log ingestion failures for custom log types sent to HTTPS Push feeds. Workaround : No workaround is required at this time. Data will be re-processed as the system recovers. |
| | 28 Oct 2026 | 12:56 PDT | Summary : Google SecOps SIEM: Log ingestion failures for HTTPS Push feeds using custom log types Description : We are experiencing an issue with Google SecOps beginning on Tuesday 2026-10-27 10:32 PDT (Exact time varies by region) Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-10-28 14:00 PDT with current details. Customer Symptoms : Google Security Operations (SecOps) Security Information and Event Management (SIEM) all customers globally are experiencing log ingestion failures for custom log types sent to HTTPS Push feeds. Workaround : No workaround is required at this time. Data will be re-processed as the system recovers. |
| | 28 Oct 2026 | 12:13 PDT | Summary : Google SecOps SIEM: Log ingestion failures for HTTPS Push feeds using custom log types Description : We are experiencing an issue with Google SecOps beginning on Tuesday 2026-10-27 10:32 PDT (Exact time varies by region) Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-10-28 12:45 PDT with current details. Customer Symptoms : Google Security Operations (SecOps) Security Information and Event Management (SIEM) all customers globally are experiencing log ingestion failures for custom log types sent to HTTPS Push feeds. Workaround : We recommend that customers pause their feeds from the source if that is an applicable option |
- All times are US/Pacific