Google Security

Incident began at 2026-06-15 00:39 and ended at 2026-06-15 04:30 (all times are US/Pacific).

We are experiencing an issue with Google SecOps search, detections and dashboards beginning on Monday, 2026-06-15 00:39 PDT in the asia-southeast1

Our engineering team is continuing to investigate the root cause and mitigation.

We will provide the next update by Monday, 2026-06-15 04:15 PDT

We apologize to all who are affected by the disruption.

Diagnosis / Customer Symptoms Customers in the impacted region may observe failures and delays while accessing Google SecOps. Customers may experience latency processing security detections as well as slower than normal …

Incident began at 2026-06-15 00:39 and ended at 2026-06-15 04:30 (all times are US/Pacific).

Google SecOps customers may have experienced higher detection latency, slower searches and dashboards in asia-southeast1

The issue with Google SecOps has been mitigated for all affected customers as of Monday, 2026-06-15 04:30 AM US/Pacific.

Detection, search, and dashboard latencies are back to normal across the asia-southeast1 region.

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

Diagnosis / Customer Symptoms Customers in the impacted region may have observed failures and delays while accessing Google SecOps. Customers may have experienced latency processing …

Incident began at 2026-06-15 00:39 and ended at 2026-06-15 04:30 (all times are US/Pacific).

We are experiencing an issue with Google SecOps search, detections and dashboards beginning on Monday, 2026-06-15 00:39 PDT in the asia-southeast1

Our engineering team is working on investigating the root cause and mitigation.

We will provide the next update by Monday, 2026-06-15 04:15 PDT

We apologize to all who are affected by the disruption.

Diagnosis / Customer Symptoms Customers in the impacted region may observe failures and delays while accessing Google SecOps. Customers may experience latency processing security detections as well as slower than normal …

Incident began at 2026-06-15 00:39 and ended at 2026-06-15 04:30 (all times are US/Pacific).

We are experiencing an issue with Google SecOps search, detections and dashboards beginning on Monday, 2026-06-15 00:39 PDT in the asia-southeast1

Our engineering team is working on investigating the root cause and mitigation.

We will provide the next update by Monday, 2026-06-15 03:15 PDT

We apologize to all who are affected by the disruption.

Diagnosis / Customer Symptoms Customers in the impacted region may observe failures and delays while accessing Google SecOps. Customers may experience latency processing security detections as well as slower than normal …

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

Summary

[Mitigated] Google SecOps customers experienced login and API request failures in multi-region:us

Description

The issue with Google SecOps has been resolved for all affected customers as of Sunday, 2026-06-14 12:23 PDT.

A recent software update caused increased intermittent login and API request failures. Our engineering team has mitigated the issue by reverting the update to a previous stable version.

Upon further investigation, our engineers confirmed the issue was limited to the US multiregion and not a global impact, and was between 05:40 PDT and …

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

Summary

[Mitigated] Google SecOps customers experienced login and API request failures in multiple regions

Description

The issue with Google SecOps has been mitigated for all affected customers as of Sunday, 2026-06-14 09:14 PDT.

Our engineering team continues to monitor the service to ensure ongoing stability.

We will provide more information by Sunday, 2026-06-14 13:30 PDT.

Symptoms

Customers across multiple regions may have experienced an increased intermittent login and API request failures.

Workaround

The issue is now mitigated.

Affected products: Google SecOps

Affected locations: Johannesburg (africa-south1), Taiwan …

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

Description

Mitigation work is still underway by our engineering team.

Preliminary data indicates that the current mitigation efforts are proceeding as expected. Our engineering team remains focused on implementing these measures and monitoring the environment to ensure continued service stability.

We will provide more information by Sunday, 2026-06-14 10:30 PDT.

Symptoms

Customers across multiple regions may have experienced an increased intermittent login and API request failures.

Workaround

None at this time.

Affected products: Google SecOps

Affected locations: Johannesburg (africa-south1), Taiwan (asia-east1), Tokyo (asia-northeast1), Seoul (asia-northeast3), Mumbai …

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

Description

We are investigating an issue with Google SecOps where some customers may experience intermittent errors in login and api requests beginning on Sunday, 2026-06-14 04:12PDT.

Our engineering team is working to identify a mitigation strategy.

We do not have an ETA for mitigation at this time.

We will provide more information by Sunday, 2026-06-14 09:30 PDT.

Symptoms

Customers across multiple regions may experience an increased intermittent login and API request failures when making API requests

Workaround

None at this time.

Affected products: Google SecOps

Affected …

Incident began at 2026-06-10 08:15 and ended at 2026-06-10 10:48 (all times are US/Pacific).

Description

The issue with Google SecOps has been resolved for all affected customers as of Wednesday, 2026-06-10 10:48 AM PDT US/Pacific.

The issue was caused by an intended down-scaling of backend compute resources in the region based on the resource utilization, which resulted in query latencies and failures. Our engineers have mitigated the issue by scaling up and restoring the necessary resources.

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

Symptoms

Impacted customers experienced errors or high latencies while loading …

Incident began at 2026-06-10 08:15 and ended at 2026-06-10 10:48 (all times are US/Pacific).

Description

Google SecOps is currently experiencing increased query latency affecting Dashboards for the following data sources: IngestionMetrics, SOAR Cases, SOAR Case History, Detections, and DataTables. Customers using HealthHub may also observe similar performance impacts.

Our engineering team has identified the issue and mitigation is in progress.

We will provide more information by Wednesday, 2026-06-10 13:00 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Symptoms

Impacted customers may experience errors or high latencies while loading their dashboards in asia-southeast1 for …

Incident began at 2026-06-08 08:11 and ended at 2026-06-09 00:46 (all times are US/Pacific).

Summary

Chronicle Security Operations customers experienced a delay in processing a subset of Emerging Threat rules.

Description

The issue with Google Security Operations (SecOps) has been mitigated for all affected users as of Tuesday, 2026-06-09 00:46 PDT and initiated reprocessing of affected rules at Tuesday, 2026-06-09 09:00 PDT.

This reprocessing will cover the last 14 days of detection coverage for affected rules. A small subset of affected rules will be reprocessed beyond 14 days.

We estimate reprocessing will complete by June 14 at the latest.

Incident began at 2026-06-08 08:11 and ended at 2026-06-09 00:46 (all times are US/Pacific).

Summary

Chronicle Security Operations customers experienced a delay in processing a subset of Emerging Threat rules.

Description

We are experiencing an issue with a subset of Emerging Threat detection within Google Security Operations (SecOps).

Our engineering team has mitigated the issue as of Tuesday, 2026-06-09 00:46 PDT, and initiated reprocessing of affected rules at Tuesday, 2026-06-09 09:00 PDT.

This reprocessing will cover the last 14 days of detection coverage for affected rules. A small subset of affected rules will be reprocessed beyond 14 days.

We …

Incident began at 2026-06-08 08:11 and ended at 2026-06-09 00:46 (all times are US/Pacific).

Summary

Chronicle Security Operations customers are experiencing delay in processing a subset of Emerging Threat rules.

Description

We are experiencing an issue with a subset of Emerging Threat detection within Chronicle Security Operations.

Our engineering team is actively implementing the mitigation. We are targeting initial mitigation to complete by Tuesday, 2026-06-09 00:00 PDT. We will initiate reprocessing of affected rules Tuesday, 2026-06-09 09:00 PDT. This reprocessing will cover the last 14 days of detection coverage. A small subset of affected rules will be reprocessed beyond …

Incident began at 2026-06-08 08:11 (all times are US/Pacific).

Summary

Chronicle Security Operations customers are experiencing delay in processing a subset of Emerging Threat rules.

Description

We are experiencing an issue with a subset of Emerging Threat detection within Chronicle Security Operations.

Our engineering team is actively implementing the mitigation. We do not have ETA at this point.

We will provide more information by Monday, 2026-06-08 16:30 PDT.

Customer Symptoms

Affected customers are experiencing delay in processing a subset of Emerging Threats rules.

Workaround

None at the time.

Affected products: Google SecOps

Affected locations: Johannesburg (africa-south1), Taiwan (asia-east1), Tokyo (asia-northeast1), …

Incident began at 2026-06-06 16:27 and ended at 2026-06-06 19:29 (all times are US/Pacific).

Description

The issue with Mandiant Threat Defense and Mandiant Managed Defense processing of Trellix alerts has been resolved for all affected customers as of Saturday, 2026-06-06 19:29 PDT

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

Symptoms

A high volume of alerts from Trellix technologies caused a processing backlog. This issue may have caused investigation reports to be delayed.

Workaround

No workaround is required, as the issue has been mitigated.

Affected products: Mandiant Hunt, Mandiant Managed Defense

Affected locations: Tokyo (asia-northeast1), …

Incident began at 2026-06-06 16:27 and ended at 2026-06-06 19:29 (all times are US/Pacific).

Description

We are experiencing an issue with Mandiant Threat Defense and Mandiant Managed Defense beginning on Saturday, 2026-06-06 16:27 PDT.

Our engineering team continues to investigate the issue.

We will provide an update by Saturday, 2026-06-06 22:15 PDT with current details.

We apologize to all who are affected by the disruption.

Symptoms

An internal alert processing issue is preventing Mandiant analysts from reviewing alerts from Trellix technologies. This issue may cause investigation reports to be delayed.

Workaround

None at this time

Affected products: Mandiant Managed …

Incident began at 2026-06-03 22:14 and ended at 2026-06-04 03:59 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps SIEM customers in the US region may have experienced delays in data ingestion for cloud-based v2 feeds.

Description

The issue with Google SecOps has been resolved for all affected users as of Thursday, 2026-06-04 03:59 PDT.

From preliminary analysis, the issue was due to an infrastructure capacity issue. Our engineers mitigated the issue by scaling up processing resources.

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

Customer Symptoms

Customers may have experienced delays in data ingestion …

Incident began at 2026-06-03 22:14 and ended at 2026-06-04 03:59 (all times are US/Pacific).

Description

Mitigation work is still underway by our engineering team. Current data indicates a significant improvement in processing throughput. The pending data backlog is steadily decreasing, and we are observing improvements in end-to-end ingestion latency for impacted customers.

We do not have a mitigation ETA at this time.

We continue to monitor the situation closely to ensure that the recovery remains stable and that all pending data is processed efficiently.

We will provide more information by Thursday, 2026-06-04 04:30 PDT with current details.

Customer Symptoms

Incident began at 2026-06-03 22:14 and ended at 2026-06-04 03:59 (all times are US/Pacific).

Description

We are experiencing an issue with Google SecOps in the US region beginning on Wednesday, 2026-06-03 22:14 PDT.

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2026-06-04 03:00 PDT with current details.

We apologize to all who are affected by the disruption.

Customer Symptoms

Customers may be experiencing delays in data ingestion in the US region for cloud-based v2 feeds.

Affected products: Google SecOps

Affected locations: Multi-region: us

Incident began at 2026-05-19 01:55 and ended at 2026-05-22 06:00 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

The issue with Google SecOps has been resolved for all affected users as of Friday, 2026-05-22 06:00 PDT.

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

Symptoms

Impacted customers might have experienced delays in the event normalization pipeline, leading to delayed detections and search results.

Workaround

None at this time.

Affected products: Google SecOps

Affected locations: Multi-region: us

Incident began at 2026-05-19 01:55 and ended at 2026-05-22 06:00 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state.

Our engineering team continues to actively work through the normalization backlog and have made significant progress in burning it down. We do not have an ETA at the moment for completion.

We will provide an update by Friday, 2026-05-22 09:30 PDT with current …

Incident began at 2026-05-19 01:55 and ended at 2026-05-22 06:00 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state.

Our engineering team continues to actively work through the normalization backlog and have made significant progress in burning it down. We do not have an ETA at the moment for completion.

We will provide an update by Thursday, 2026-05-21 18:00 PDT with current …

Incident began at 2026-05-19 01:55 and ended at 2026-05-22 06:00 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state. Our engineering team continues to actively work through the normalization backlog and have made significant progress in burning it down. We do not have an ETA at the moment for completion.

We will provide an update by Thursday, 2026-05-21 15:00 PDT with current …

Incident began at 2026-05-19 01:55 and ended at 2026-05-22 06:00 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state. Our engineering team continues to actively work through the normalization backlog and have made significant progress in burning it down. We do not have an ETA at the moment for completion.

We will provide an update by Thursday, 2026-05-21 13:00 PDT with current …

Incident began at 2026-05-19 01:55 and ended at 2026-05-22 06:00 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state. Our engineering team continues to actively work through the normalization backlog and have made significant progress in burning it down. We do not have an ETA at the moment for completion.

We will provide an update by Thursday, 2026-05-21 10:00 PDT with current …

Incident began at 2026-05-19 01:55 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state. Our engineering team continues to actively work through the normalization backlog and have made significant progress in burning it down. We do not have an ETA at the moment for completion.

We will provide an update by Thursday, 2026-05-21 06:00 PDT with current details.

We apologize to all …

Incident began at 2026-05-19 01:55 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state. Our engineering team continues to actively work through the normalization backlog and have made significant progress in burning it down. We do not have an ETA at the moment for completion.

We will provide an update by Thursday, 2026-05-21 04:00 PDT with current details.

We apologize to all …

Incident began at 2026-05-19 01:55 (all times are US/Pacific).

Summary

[Mitigated] Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state. Our engineering continue to actively work through the normalization backlog and have made significant progress in burning it down. We do not have an ETA at the moment for completion.

We will provide an update by Thursday, 2026-05-21 00:30 PDT with current details.

We apologize to all who …

Incident began at 2026-05-20 14:58 and ended at 2026-05-20 22:29 (all times are US/Pacific).

Summary

Mandiant Threat Defense and Mandiant Managed Defense customers may be experiencing delayed alert triage and investigation.

Description

We are experiencing an issue with Mandiant Threat Defense and Mandiant Managed Defense beginning on Wednesday, 2026-05-20 14:58 PDT.

Our engineering team continues to investigate the issue. We are partially mitigating the issue by slowly clearing the backlog but newly ingested alerts will continue to be delayed.

We will provide an update by Wednesday, 2026-05-20 23:30 PDT with current details.

We apologize to all who are affected …

Incident began at 2026-05-20 14:58 and ended at 2026-05-20 22:29 (all times are US/Pacific).

Summary

Mandiant Threat Defense and Mandiant Managed Defense customers may have experienced delayed alert triage and investigation.

Description

The issue with Mandiant Threat Defense and Mandiant Managed Defense has been mitigated as of Wednesday, 2026-05-20 22:29 US/Pacific.

The issue was caused by excessively large detections from a third-party vendor signature that consumed processing resources and slowed the processing of other detections.

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

Customer Symptoms

An internal alert processing issue delayed Mandiant analysts from …

Incident began at 2026-05-20 14:58 and ended at 2026-05-20 22:29 (all times are US/Pacific).

Summary

Mandiant Threat Defense and Mandiant Managed Defense customers may be experiencing delayed alert triage and investigation.

Description

We are experiencing an issue with Mandiant Threat Defense and Mandiant Managed Defense beginning on Wednesday, 2026-05-20 14:58 PDT.

Our engineering team continues to investigate the issue.

We will provide an update by Wednesday, 2026-05-20 20:30 PDT with current details.

We apologize to all who are affected by the disruption.

Customer Symptoms

An internal alert processing issue is preventing Mandiant analysts from reviewing alerts. Data ingestion from …

Incident began at 2026-05-19 01:55 (all times are US/Pacific).

Summary

Google SecOps had experienced pipeline delays.

Description

Between Tuesday, 2026-05-19 01:55 PDT to Wednesday, 2026-05-20 16:37 PDT customers in multiregion/us might have experienced pipeline delays.

Our internal telemetry shows that the Live data processing operations have returned to normal state. Our engineering team is currently working through a backlog of normalized events. We do not have an ETA at the moment for backlog completion.

We will provide an update by Wednesday, 2026-05-20 20:30 PDT with current details.

We apologize to all who are affected by the disruption.

Symptoms

Impacted …