← Back to the carnage
GCP
🔴 Google's VMware Engine decided zones weren't worth talking to each other. Multi-region connectivity is playing dead while engineers dust off the VMware manual they swore they'd never need. Stretched clusters are now just... unstretched.
// The official story
UPDATE: Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.
// Status page says
Incident began at 2026-07-14 10:00 (all times are US/Pacific ). Summary Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. Description We are experiencing an issue with Google Cloud VMware Engine (GCVE) beginning Tuesday, 2026-07-14 at 10:00 PDT.
🔗 Official status page (for the PR-approved version)
https://status.cloud.google.com/incidents/T8gmtofFSTGT5tbhyciFGcp's Greatest Hits
⚪ GCP
4d ago
⚪ Google Cloud Storage decided uploads were optional for 11 hours straight. Write operations moved at glacial speeds—and not the scenic kind. Incident lasted from early morning through afternoon Pacific time, turning 'cloud storage' into 'cloud sluggish.'
⚪ GCP
Sep 01, 2026
⚪ Google's us-central1-b zone decided to ghost half its services for 4 hours straight. The other zones watched from a safe distance, unbothered and fully functional. A masterclass in zone-level commitment issues.
🟢 GCP
Aug 20, 2026
⚪ us-west1 region decided to take an unscheduled nap from 8:40 AM to 12:20 PM, treating timeouts like they were going out of style. Engineers emerged from the war room with the all-clear, though 'mitigation complete' is corporate for 'we turned it off and back on.'. (Auto-resolved: no updates in 24h)
🟢 GCP
Jul 16, 2026
⚪ Update: RESOLVED: Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solutions (