Google engineer unplugged every fiber they could see and – surprise! – took down a chunk of the G-Cloud
- ID
- 21399
- Status
- summarized
- Published
- 04 Sep 2026, 12:48 PM
- Fetched
- 04 Sep 2026, 2:30 PM
- Provider
- The Register
- Category
- technology
- Original URL
- https://www.theregister.com/off-prem/2026/09/04/google-engineer-unplugged-every-fiber-they-could-see-and-surprise-took-down-a-chunk-of-the-g-cloud/5294418
- Source URL
- https://www.theregister.com/headlines.atom
Summary
- Score
- 6.5
- Created
- 04 Sep 2026, 2:30 PM
- Tags
- Audience
- developersvibe_codersdatabase_learnerssaas_founders
What happened
A Google Cloud engineer performing routine hardware maintenance in us-central1-b sequentially unplugged 100% of fiber-optic cables across all network devices within 13 minutes, defeating Google's multi-path redundancy design and causing a partial outage from 07:41 to 11:52 PT on September 1, 2026. Traffic drop rates hit 100% for affected VMs, which could still communicate with each other but were unreachable from outside. Google restored service by shifting traffic to healthy capacity elsewhere in the region.
Why it matters
If you run multi-region or multi-zone workloads on GCP, this confirms that a single zone in us-central1-b can go fully dark from human error despite Google's redundancy claims—so don't treat any one zone as safe for production traffic. It's also a concrete reminder that physical-layer procedures, not just software failures, can defeat your cloud provider's SLA assumptions.
Discussion angle
What does this incident tell us about the gap between designed redundancy (multiple fiber paths, diverse power) and operational reality—and how should small teams on GCP practically hedge against a single zone going 100% offline?