β Back to the carnage
GCP
π΄ Vertex AI's Gemini API decided error rates were the real intelligent response. Global endpoint spent Friday morning having an existential crisis, rejecting requests like a moody teenager. Crisis averted by 6:45 AM, but your Friday morning coffee break got longer. (Auto-resolved: no updates in 24h)
// The official story
UPDATE: Vertex AI Gemini API customers experienced increased error rates when accessing the global endpoint.
// Status page says
Incident began at 2026-02-27 04:36 and ended at 2026-02-27 06:45 (all times are US/Pacific ). Description Between Friday, 2026-02-27, 04:36 and 06:45 PST, customers experienced increased error rates when accessing the Vertex Gemini API Global endpoint. The issue impacted API requests to multiple Gemini models. The incident also caused downstream imp
π Official status page (for the PR-approved version)
https://status.cloud.google.com/incidents/41E5S3mkTGDfkZuJZH5kGcp'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 (