Google Security
Google Security
Last checked: Oct 27, 2026 17:01
Uptime (Last 90 Days)
3.33%Incident History (Last 30 Days)
RESOLVED: Google SecOps customers in the EU multi-region may experience delays with data normalization, search and detections.
Incident began at 2026-10-26 05:09 and ended at 2026-10-26 08:10 (all times are US/Pacific).
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.
Affected products: Google SecOps
Affected locations: Multi-region: europe, Warsaw (europe-central2), Finland (europe-north1), Belgium (europe-west1), Turin (europe-west12), …
Oct 26, 2026
15:37
UPDATE: Google SecOps customers in the EU multi-region may experience delays with data normalization, search and detections.
Incident began at 2026-10-26 05:09 and ended at 2026-10-26 08:10 (all times are US/Pacific).
Summary Google SecOps customers in the EU multi-region may experience delays with data normalization, search and detections.
Description We are experiencing an issue with Google SecOps in the EU multi-region causing delays in data normalization, search and detections for customers, starting on Monday, 2026-10-26 05:09 PDT.
Log ingestion remains operational, and ingested data is safely queued and will be processed as backlog clears.
Our Product Engineering Team is actively investigating and deploying mitigations to relieve processing latency.
We will provide our next update by Monday, …
Oct 26, 2026
15:37
RESOLVED: The issue affecting Google SecOps (SIEM and SOAR) customers in the europe-west2 region has been mitigated.
Incident began at 2026-10-19 23:08 and ended at 2026-10-20 04:50 (all times are US/Pacific).
Description
The issue with Google SecOps (SIEM and SOAR) in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT has been mitigated for all affected customers as of Tuesday, 2026-10-20 04:50 PDT.
Due to a power event we had suffered an outage within europe-west2. The power event is mitigated and Engineering teams completed mitigation steps to restore full availability.
We thank you for your patience while we worked to resolve this issue.
Symptoms
All session connection failures, Normalization, Visualization, and Detections issues have been fully mitigated and …
Oct 20, 2026
12:12
UPDATE: The issue affecting Google SecOps (SIEM and SOAR) customers in the europe-west2 region has been mitigated.
Incident began at 2026-10-19 23:08 and ended at 2026-10-20 04:50 (all times are US/Pacific).
Description
We are investigating an ongoing incident affecting Google Security Operations SIEM and SOAR services in the europe-west2 region beginning on Monday, 2026-10-19 23:08 PDT.
Our Product and Engineering teams are actively engaged to restore full availability.
We will provide an update by Tuesday, 2026-10-20 04:00 PDT with current details.
We apologize to all who are affected by the disruption.
Symptoms
Impacted customers may experience session connection failures when accessing Google Security Operations, as well as delays with platform workflows (including normalization and detections).
Workaround
…Oct 20, 2026
12:11
UPDATE: The issue affecting Google SecOps (SIEM and SOAR) customers in the europe-west2 region has been mitigated.
Incident began at 2026-10-19 23:08 and ended at 2026-10-20 04:50 (all times are US/Pacific).
Description
We are investigating an incident affecting Google Security Operations (SIEM and SOAR) in the europe-west2 region that began on Monday, 2026-10-19 23:08 PDT.
Our Product and Engineering teams are actively working to restore full availability.
We will provide an update by Tuesday, 2026-10-20 04:00 PDT with current details.
We apologize to all who are affected by the disruption.
Symptoms
Impacted customers may experience session connection failures when accessing Google Security Operations, as well as delays with platform workflows (including normalization and detections).
Workaround
None …
Oct 20, 2026
09:47
UPDATE: The issue affecting Google SecOps (SIEM and SOAR) customers in the europe-west2 region has been mitigated.
Incident began at 2026-10-19 23:08 and ended at 2026-10-20 04:50 (all times are US/Pacific).
Description
We are investigating an incident affecting Google Security Operations (SIEM and SOAR) in the europe-west2 region that began on Monday, 2026-10-19 23:08 PDT.
Our Product and Engineering teams are actively working to restore full availability.
We will provide an update by Tuesday, 2026-10-20 02:30 PDT with current details.
We apologize to all who are affected by the disruption.
Symptoms
Impacted customers may experience session connection failures when accessing Google Security Operations, as well as delays with platform workflows (including normalization and detections).
Workaround
None …
Oct 20, 2026
09:25
RESOLVED: Google Security Operations (SIEM) customers may experience brief, intermittent delays or errors when running searches.
Incident began at 2026-10-18 09:42 and ended at 2026-10-19 07:49 (all times are US/Pacific).
Description
The intermittent network delays affecting search queries in Google Security Operations (SIEM) have been resolved as of Monday, 2026-10-19 07:49 US/Pacific.
We thank you for your patience while we worked to resolve this issue.
Symptoms
Google SecOps customers in US, Europe and Asia may have experienced brief, intermittent latency spikes or timeouts when running searches in the Google Security Operations UI or API. Log ingestion, parsing, and detection rules remained healthy and operational.
Workaround
The issue is mitigated.
Affected products: Google SecOps
Affected locations: Johannesburg …
Oct 19, 2026
19:59
UPDATE: Google Security Operations (SIEM) customers may experience brief, intermittent delays or errors when running searches.
Incident began at 2026-10-18 09:42 and ended at 2026-10-19 07:49 (all times are US/Pacific).
Summary
Google Security Operations (SIEM) customers may experience brief, intermittent delays or errors when running searches.
Description
We are investigating intermittent network delays affecting search queries in Google Security Operations (SIEM) starting on Sunday, 2026-10-18 09:42 US/Pacific.
The Product Engineering Team is actively working to prevent recurring search delays. Log ingestion and detections are not impacted, and no data has been lost.
We will provide our next update by Monday, 2026-10-19 13:30 US/Pacific.
Diagnosis / Customer Symptoms
All customers in US and Europe may experience …
Oct 19, 2026
19:59
RESOLVED: Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1
Incident began at 2026-10-15 11:22 and ended at 2026-10-15 12:10 (all times are US/Pacific).
Summary : Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1
Description : The issue with Google SecOps has been resolved for all affected projects as of Thursday, 2026-10-15 12:10 PDT.
Based on our initial analysis, the incident was triggered by transient underlying network connectivity issues in the US region, which led to write contention in the backend indexing storage layer and retry queue backlogs.
We mitigated the impact by isolating the high-volume traffic pattern to relieve storage contention and …
Oct 15, 2026
20:02
UPDATE: Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1
Incident began at 2026-10-15 11:22 and ended at 2026-10-15 12:10 (all times are US/Pacific).
Summary : Elevated Indexing Latency and Errors for Google Security Operations (SecOps) SIEM in us-central1, us-east1
Description : We are experiencing an issue with Google SecOps beginning on Thursday, 2026-10-15 11:22 PDT.
Our engineering team continues to investigate the issue.
We will provide an update by Thursday, 2026-10-15 12:45 PDT with current details.
We apologize to all who are affected by the disruption.
Symptoms
Customers using Google SecOps in the US region (us-central1, us-east1) may experience elevated latency during log ingestion, normalization, and indexing. As …
Oct 15, 2026
20:02
RESOLVED: 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).
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 …
Oct 14, 2026
21:33
UPDATE: 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).
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.
Affected …
Oct 14, 2026
21:23
UPDATE: 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).
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.
Affected products: Google SecOps
Affected locations: Sydney (australia-southeast1), Tel Aviv (me-west1)
Oct 14, 2026
20:33
UPDATE: 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).
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.
Affected products: Google SecOps
Affected locations: Sydney (australia-southeast1), Tel Aviv (me-west1)
Oct 14, 2026
20:15
UPDATE: 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).
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.
Affected products: Google SecOps
Affected locations: Sydney (australia-southeast1), Tel Aviv (me-west1)
Oct 14, 2026
20:06
RESOLVED: Some Google SecOps customers will not have received alerts for curated detection ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644.
Incident began at 2026-09-30 12:34 and ended at 2026-10-08 07:30 (all times are US/Pacific).
Title
Some Google SecOps customers will not have received alerts for curated detection ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644.
Description
Google SecOps curated rule ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644 was updated on Saturday, 2026-09-26 12:34 US/Pacific. As part of the update process, the rule was not redeployed, and did not create alerts even if enabled prior to 2026-09-26 12:34 US/Pacific.
The 2026-09-26 update process moved rule ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644 to the Mandiant Intel Emerging Threats detection rule pack, and will have inherited the detection and alerting configurations for that pack.
Backfill was only applied to customers …
Oct 08, 2026
15:09
UPDATE: Some Google SecOps customers will not have received alerts for curated detection ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644.
Incident began at 2026-09-30 12:34 and ended at 2026-10-08 07:30 (all times are US/Pacific).
Title
Some Google SecOps customers will not have received alerts for curated detection ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644.
Description
Google SecOps curated rule ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644 was updated on Saturday, 2026-09-26 12:34 US/Pacific. As part of the update process, the rule was not redeployed, and would not create alerts even if enabled prior to 2026-09-26 12:34 US/Pacific.
We are currently in the process of backfilling the rule to 2026-09-26 12:34 US/Pacific and targeting backfill completion by Thursday, 2026-10-08 17:00 PDT.
We will provide an update by Thursday, 2026-10-08 18:00 PDT with …
Oct 08, 2026
15:08
UPDATE: Some Google SecOps customers will not have received alerts for curated detection ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644.
Incident began at 2026-09-30 12:34 and ended at 2026-10-08 07:30 (all times are US/Pacific).
Title
Some Google SecOps customers will not have received alerts for curated detection ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644.
Description
Google SecOps curated rule ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644 was updated on Saturday, 2026-09-26 12:34 US/Pacific. As part of the update process, the rule was not redeployed, and would not create alerts even if enabled prior to 2026-09-26 12:34 US/Pacific.
We are currently in the process of backfilling the rule to 2026-09-26 12:34 US/Pacific and targeting backfill completion by Wednesday, 2026-10-07 17:00 PDT.
We will provide an update by Wednesday, 2026-10-07 18:00 PDT with …
Oct 08, 2026
00:48
UPDATE: Some Google SecOps customers will not have received alerts for curated detection ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644.
Incident began at 2026-09-30 12:34 (all times are US/Pacific).
Title
Some Google SecOps customers will not have received alerts for curated detection ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644.
Description
Google SecOps curated rule ur_A6694B54-4A6B-4620-8B64-9D02AD0A8644 was updated on 2026.09.26 12:34 PDT. As part of the update process, the rule was not redeployed, and would not create alerts even if enabled prior to 2026.09.26 12:34 PDT.
We are currently in the process of backfilling the rule to 2026.09.26 12:34 PDT. We will provide an update once the backfill is complete.
We are currently in the process of backfilling the rule to 2026.09.26 12:34 PDT. We will …
Oct 06, 2026
22:50
RESOLVED: Some Google SecOps customers may experience delayed UDM Search and detections in the US region.
Incident began at 2026-10-05 20:45 and ended at 2026-10-06 04:00 (all times are US/Pacific).
Title
Some Google SecOps customers may have experienced delayed Search and detections in the US regions.
Description
The issue with Google SecOps Search and Detections in the US multi-regions has been mitigated for all affected customers as of Tuesday, 2026-10-06 04:00 US/Pacific.
From preliminary analysis, the issue was triggered by a backend network disruption.
Our engineers mitigated the issue by resolving the network disruption.
We thank you for your patience while we worked on mitigating the issue.
Symptoms
Affected customers in US multi-regions may have …
Oct 06, 2026
11:15
UPDATE: Some Google SecOps customers may experience delayed UDM Search and detections in the US region.
Incident began at 2026-10-05 20:45 and ended at 2026-10-06 04:00 (all times are US/Pacific).
Title
Some Google SecOps customers may experience delayed Search and detections in the US region.
Description
We are experiencing an issue with Google SecOps Search and Detections in the US multi-region beginning on Monday, 2026-10-05 20:45 PDT.
Our engineering team continues to investigate the issue while working on multiple mitigation strategies in parallel.
We will provide an update by Tuesday, 2026-10-06 06:00 PDT with current details.
Symptoms
Affected customers in US multi-region may experience delays in Search and Detection.
Workaround
None at this time.
Affected …
Oct 06, 2026
11:15
UPDATE: Some Google SecOps customers may experience delayed UDM Search and detections in the US region.
Incident began at 2026-10-05 20:45 and ended at 2026-10-06 04:00 (all times are US/Pacific).
Title
Some Google SecOps customers may experience delayed UDM Search and detections in the US region.
Description
We are experiencing an issue with Google SecOps UDM Search and Detections in the US multi-region beginning on Monday, 2026-10-05 20:45 PDT.
Our engineering team continues to investigate the issue while working on a mitigation strategy in parallel.
We currently do not have an estimated time for mitigation.
We will provide an update by Tuesday, 2026-10-06 02:30 PDT with current details.
We apologize to all who are affected …
Oct 06, 2026
09:23
RESOLVED: Elevated error rates and latency affecting Chronicle Search & Rules in the US has been mitigated.
Incident began at 2026-10-01 11:37 and ended at 2026-10-01 12:30 (all times are US/Pacific).
Summary
Elevated error rates and latency affecting Chronicle Search & Rules in the US has been mitigated.
Description
The elevated error rates and latency affecting Chronicle Search & Rules in the US region has been mitigated on Thursday, 2026-10-01 12:30 PDT.
While we are still performing root cause analysis, preliminary analysis indicates that the issue was triggered due to localized infrastructure failure. We rerouted query traffic from the affected infrastructure to healthy infrastructure.
We thank you for your patience while we worked on mitigating the …
Oct 01, 2026
20:43
UPDATE: Some Google SecOps customers may experience increased search latencies and intermittent error rates in the US region.
Incident began at 2026-09-30 00:31 and ended at 2026-09-30 01:44 (all times are US/Pacific).
Summary
Some Google SecOps customers may experience increased search latencies and intermittent error rates in the US region.
Description
We are experiencing an issue with Google Secops Search in the US multi-region beginning on Wednesday, 2026-09-30 00:31 PDT.
Our engineering team continues to investigate the issue.
We will provide an update by Wednesday, 2026-09-30 03:30 PDT with current details.
We apologize to all who are affected by the disruption.
Customer Symptoms
Affected customers in US multi-region may experience high Search latency and search failures as …
Sep 30, 2026
09:37
RESOLVED: Some Google SecOps customers may experience increased search latencies and intermittent error rates in the US region.
Incident began at 2026-09-30 00:31 and ended at 2026-09-30 01:44 (all times are US/Pacific).
Summary
Some Google SecOps customers may have experienced increased search latencies and intermittent error rates in the US region.
Description
The issue with Google SecOps has been mitigated for all affected users as of Wednesday, 2026-09-30 01:44 US/Pacific.
Service performance was successfully restored after addressing the resource contention that caused the temporary disruption.
We thank you for your patience while we worked on mitigating the issue.
Diagnosis / Customer Symptoms
Affected customers in US multi-region may have experienced high Search latency and search failures as …
Sep 30, 2026
09:37
UPDATE: Data normalization and detection processing delays in the EU region has been mitigated.
Incident began at 2026-09-29 05:26 and ended at 2026-09-29 09:00 (all times are US/Pacific).
Summary
We are providing an update on the normalization and detection processing delays affecting Google SecOps customers in the EU region, which began on Tuesday, 2026-09-29 05:26 PDT.
Our engineering team continues to investigate the issue and is actively working to restore normal processing speeds. Ingested log data remains safely queued and will continue to process automatically. No data loss has occurred, and no customer action is required.
We will provide a further update by Tuesday, 2026-09-29 09:30 PDT with current details.
We apologize to …
Sep 29, 2026
16:18
RESOLVED: Data normalization and detection processing delays in the EU region has been mitigated.
Incident began at 2026-09-29 05:26 and ended at 2026-09-29 09:00 (all times are US/Pacific).
Summary
The normalization and detection processing delays affecting Google SecOps customers in the EU region have been mitigated on Tuesday, 2026-09-29 09:00 PST.
From preliminary analysis, the issue was triggered by resource contention and we added additional resources to resolve the issue.
We thank you for your patience while we worked on mitigating the issue.
Symptoms
Processing delays in the EU region are affecting the speed at which ingested log data is normalized and security detections are generated.
Workaround
The issue is now mitigated.
Affected …
Sep 29, 2026
16:18
UPDATE: Data normalization and detection processing delays in the EU region has been mitigated.
Incident began at 2026-09-29 05:26 and ended at 2026-09-29 09:00 (all times are US/Pacific).
Summary
We are experiencing an issue with Google SecOps in EU, beginning on Tuesday, 2026-09-29 05:26 PDT.
Our engineering team continues to investigate the issue. We will provide more information by Tuesday, 2026-09-29 07:30 PDT with current details.
We apologize to all who are affected by the disruption.
Symptoms
Impacted users in EU may experience delays with data normalization and detections.
Workaround
None at this time. Ingested log data is safely queued and will be normalized automatically without requiring customer action.
Affected products: Google SecOps
Affected …
Sep 29, 2026
14:30
RESOLVED: Google SecOps is experiencing intermittent login failures and HTTP 500 errors in us-east1, us-central1, and europe-west1; mitigation is underway.
Incident began at 2026-09-28 06:30 and ended at 2026-09-28 14:30 (all times are US/Pacific).
Title:
Google SecOps intermittent login and API errors in us-east1, us-central1, and europe-west1 have been mitigated; service has returned to normal.
Description:
The issue affecting Google SecOps platform access and API calls in us-east1, us-central1, and europe-west1 has been successfully mitigated for all affected customers as of Monday, 2026-09-28 14:30 PDT.
From preliminary analysis, the issue was triggered by a recent software update. Our engineering team mitigated the issue by rolling back the update for recently updated customers to restore service to normal.
If you …
Sep 28, 2026
21:37
UPDATE: Google SecOps is experiencing intermittent login failures and HTTP 500 errors in us-east1, us-central1, and europe-west1; mitigation is underway.
Incident began at 2026-09-28 06:30 and ended at 2026-09-28 14:30 (all times are US/Pacific).
Description:
Earlier mitigation attempts did not mitigate the issue and further mitigation efforts are continuing across the impacted instances. We anticipate this to complete within the next few hours. Following these actions, full service restoration and normal access are expected. Furthermore, these mitigation steps are not expected to cause any data loss or customer impact.
Customers in affected projects across us-east1, us-central1, and europe-west1 may encounter intermittent HTTP 500 errors or authentication failures when attempting to access the platform.
Google SecOps (Log Ingestion, Search, Detection …
Sep 28, 2026
21:37
UPDATE: Google SecOps is experiencing intermittent login failures and HTTP 500 errors in us-east1, us-central1, and europe-west1; mitigation is underway.
Incident began at 2026-09-28 06:30 and ended at 2026-09-28 14:30 (all times are US/Pacific).
Description:
Mitigation efforts are currently underway across the impacted instances and are anticipated to wrap up within the next hour. Following these actions, full service restoration and normal access are expected. Furthermore, these mitigation steps are not expected to cause any data loss or customer impact.
Customers in affected projects across us-east1, us-central1, and europe-west1 may encounter intermittent HTTP 500 errors or authentication failures when attempting to access the platform.
Google SecOps (Log Ingestion, Search, Detection Rules, and Dashboards) and all other geographic regions remain …
Sep 28, 2026
18:59
UPDATE: Google SecOps is experiencing intermittent login failures and HTTP 500 errors in us-east1, us-central1, and europe-west1; mitigation is underway.
Incident began at 2026-09-28 06:30 and ended at 2026-09-28 14:30 (all times are US/Pacific).
Description:
We are investigating an intermittent issue with Google SecOps beginning at Monday, 2026-09-28 06:30 US/Pacific.
Customers in affected projects across us-east1, us-central1, and europe-west1 may encounter intermittent HTTP 500 errors or authentication failures when attempting to access the platform.
Our engineering team has acknowledged the issue and mitigation is actively underway. We expect service stability and normal access to be fully restored shortly. No customer impact or data loss is expected as a result of the mitigation actions.
Google SecOps (Log Ingestion, Search, Detection …
Sep 28, 2026
18:00
UPDATE: Google SecOps is experiencing intermittent login failures and HTTP 500 errors in us-east1, us-central1, and europe-west1; mitigation is underway.
Incident began at 2026-09-28 06:30 and ended at 2026-09-28 14:30 (all times are US/Pacific).
Description:
We are experiencing an intermittent issue with Google SecOps beginning at Monday, 2026-09-28 06:30 US/Pacific.
Customers in affected projects across us-east1, us-central1, and europe-west1 may encounter intermittent HTTP 500 errors or failures when attempting to log in to the SecOps platform or perform API calls.
Ingestion and SIEM APIs are unaffected by the issue.
Our engineering team continues to investigate the issue and is actively testing mitigations.
We will provide more information by Monday, 2026-09-28 10:00 US/Pacific with current details.
Symptoms:
Google SecOps is …
Sep 28, 2026
17:11
UPDATE: Google SecOps is experiencing intermittent login failures and HTTP 500 errors in us-east1, us-central1, and europe-west1; mitigation is underway.
Incident began at 2026-09-28 06:30 and ended at 2026-09-28 14:30 (all times are US/Pacific).
Description:
We are experiencing an intermittent issue with Google SecOps beginning at Monday, 2026-09-28 06:30 US/Pacific.
Customers in affected projects across us-east1, us-central1, and europe-west1 may encounter intermittent HTTP 500 errors or failures when attempting to log in to the SecOps platform or perform API calls.
Ingestion and SIEM APIs are unaffected by the issue.
Our engineering team continues to investigate the issue and is actively testing mitigations.
We will provide more information by Monday, 2026-09-28 09:00 US/Pacific with current details.
We apologize to all …
Sep 28, 2026
16:01