---
title: "Google SecOps U.S. network disruption"
description: "Over eight hours of elevated latency and intermittent errors affecting search, detection, and dashboards"
incident_type: "Operational outage"
status: "active"
last_modified: "2026-11-17"
canonical_url: "https://www.ally.security/incidents/google-secops-us-network-disruption-2026"
markdown_url: "https://www.ally.security/incidents/google-secops-us-network-disruption-2026.md"
stix_url: "https://www.ally.security/incidents/google-secops-us-network-disruption-2026/stix.json"
---

# Google SecOps U.S. network disruption

Over eight hours of elevated latency and intermittent errors affecting search, detection, and dashboards.

Last modified Nov 17, 2026 · 1 source

## Summary

- **Environment:** Google SecOps U.S. multi-region
- **Operational impact:** Over eight hours of elevated latency and intermittent errors affecting search, detection, and dashboards
- **Financial impact:** Financial impact remains unquantified in public reports

## What happened

On November 11, 2026, [Google SecOps](https://cloud.google.com/security/products/security-operations) experienced degraded performance in its U.S. multi-region. Google’s [status report](https://status.cloud.google.com/security/incidents/1sSrwjq5t9bK41xTazW7) places the start at 2:07 p.m. Pacific time and recovery at 10:30 p.m. Pacific time. [1](#source-1)

## Impact

- Customers could experience elevated latency and intermittent, retryable errors in searches, detections, and dashboard queries. [1](#source-1)

## Timeline

### November 11, 2026 — Google SecOps degradation begins

Searches, detections, and dashboards were affected in the U.S. multi-region. [1](#source-1)

### November 12, 2026 — Google confirms customer impact ended

Google reported that the issue had stopped at 10:30 p.m. Pacific time on November 11. [1](#source-1)

### November 17, 2026 — Briefing updated

This briefing was last reviewed and updated on November 17, 2026.

## Threat Group & Attack Vector

Google attributed the degradation to physical damage to a vendor-managed network. The damage temporarily reduced the available capacity for traffic between several regions. [1](#source-1)

## Response

Google routed traffic around the affected paths and prioritized critical traffic. It monitored system stability and confirmed recovery for affected users. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/google-secops-us-network-disruption-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Google SecOps U.S. service disruption notice

official · Google · Nov 11, 2026

<https://status.cloud.google.com/security/incidents/1sSrwjq5t9bK41xTazW7>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Google SecOps U.S. network disruption: Customers could experience elevated latency and intermittent, retryable errors in searches, detections, and dashboard queries.
2. **Occurred At · 100% confidence · current**  
   Google confirms customer impact ended: 2026-11-12T06:30:00Z
3. **Affected Organization · 100% confidence · current**  
   Google SecOps U.S. network disruption: Google
4. **Resulted In · 100% confidence · current**  
   Google SecOps U.S. network disruption: On November 11, 2026, Google SecOps experienced degraded performance in its U.S. multi-region. Google’s status report places the start at 2:07 p.m. Pacific time and recovery at 10:30 p.m. Pacific time.
5. **Resulted In · 100% confidence · current**  
   Google SecOps U.S. network disruption: Google attributed the degradation to physical damage to a vendor-managed network. The damage temporarily reduced the available capacity for traffic between several regions.
6. **Occurred At · 100% confidence · current**  
   Google SecOps degradation begins: 2026-11-11T22:07:00Z
7. **Resulted In · 100% confidence · current**  
   Google SecOps U.S. network disruption: Google routed traffic around the affected paths and prioritized critical traffic. It monitored system stability and confirmed recovery for affected users.

</details>
