Google SecOps U.S. network disruption

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

Last modified

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
  • Record status: Developing record. Reviewed November 17, 2026; updated as evidence emerges.

What happened

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. [1]

Impact

  • Customers could experience elevated latency and intermittent, retryable errors in searches, detections, and dashboard queries. [1]

Timeline

  1. Google SecOps degradation begins

    Searches, detections, and dashboards were affected in the U.S. multi-region.

    [1]
  2. Google confirms customer impact ended

    Google reported that the issue had stopped at 10:30 p.m. Pacific time on November 11.

    [1]
  3. 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]

Response

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