← Back to the carnage
GCP
⚪ 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.
// The official story
RESOLVED: Multiple products in us-central1-b are experiencing network service degradation.
// Status page says
Incident began at 2026-09-01 07:44 and ended at 2026-09-01 11:52 (all times are US/Pacific ). Summary Multiple products in us-central1-b are experiencing network service degradation. Description The issue is affecting a portion of the us-central1-b zone. The remaining zones in the region are unaffected. Most of the pro
🔗 Official status page (for the PR-approved version)
https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8EvGcp'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
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 (
🟢 GCP
Jul 16, 2026
🔴 GCVE, NetApp Volumes, and Bare Metal Solutions melting in europe-west4-a after cooling system decided to take an unscheduled siesta. Datacenters apparently run on optimism and ductape. Google's AC unit ghosted harder than a bad dating app match.