GCP

🟠 Google Cloud's Indian routes decided to play hide-and-seek with packets for 21 days. Delhi, Chennai, and Mumbai users experienced latency spikes and mysterious packet loss—turns out the infrastructure needed a spiritual journey. Now resolved, probably. (Auto-resolved: no updates in 24h)

⏰ Jun 29, 2026 Fixed (for now) spotted via status_rss

// The official story

RESOLVED: Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss.

// Status page says

Incident began at 2026-06-05 00:00 and ended at 2026-06-26 12:00 (all times are US/Pacific ). Summary Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas experienced intermittent periods of elevated latency and possible packet loss. Description Traffic rerouting from the impacted Delh

🔗 Official status page (for the PR-approved version)

https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr

Gcp'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 (