A major Google Cloud Platform (GCP) outage that began midday Thursday, June 12 (Pacific) triggered a ripple of downtime across the internet, briefly disrupting Spotify, Discord, Snapchat, Cloudflare services, OpenAI apps, Replit and dozens of websites. Google has now confirmed that all services are fully restored, while third‑party platforms report normal operations.
What Happened?
| Timeline (UTC) | Event | Impacted Services |
|---|---|---|
| 14:51 | Invalid automated quota update hit Google Cloud’s API Management system | GCP APIs, Google Chat, Meet, Gmail, Drive, Calendar, Voice ( |
| 15:20–22:18 | Requests to Google Identity failed → auth errors | Spotify log‑ins, Discord embeds, Snapchat, Anthropic, Shopify |
| 18:34–21:02 | Cloudflare Workers KV outage (storage backend) | KV‑dependent sites, some CDN assets |
| 21:30 | Downdetector shows 20 k+ Spotify complaints; peaks at 14.7 k for Google services | End‑user streaming & log‑ins |
| 22:18 | Google Cloud reports “issue mitigated” | Gradual recovery across apps |
| June 13 09:37 | Google posts mini‑incident report & apology | Root cause: bad quota push; promises safeguards |
Current Service Status
| Platform | Status (June 13, 19:00 IST) | Notes |
|---|---|---|
| Google Cloud | ✅ Operational | All 50+ affected products back online |
| Cloudflare | ✅ Operational | 2 h 28 m outage resolved; root cause in Workers KV storage |
| Spotify | ✅ Operational | Log‑ins & playback normal; incident closed |
| Discord | ✅ Operational | Minor DM error fixed; no incidents today |
| AWS | ✅ Operational | No outages reported today |
Why It Mattered
- Centralized authentication: Many consumer apps rely on Google Cloud Identity; a single mis‑configuration cascaded everywhere.
- Cloud concentration risk: Outage underlined dependence on a handful of hyperscalers (GCP, AWS, Azure).
- Visibility gap: Early Downdetector spikes outpaced official dashboards by ~30 minutes, highlighting user reliance on third‑party monitoring.
See Also – Anker Recalls Over 1 Million Power Banks Over Fire and Burn Hazards
What Google Promised Next
- “Safeguarded quota pushes” – extra validation layers before global rollout.
- Regional kill‑switch to stop a faulty update from propagating worldwide.
- Full public post‑mortem within 10 business days.
Quick Takeaways for IT Teams
- Multi‑cloud failover remains critical; even brief identity outages can stall customer apps.
- Keep status pages & incident RSS feeds wired into alert systems.
- Use graceful‑degradation paths (cached tokens, read‑only modes) for third‑party auth.
Final Note –
All services are now back online, but the outage shows how fragile our internet truly is when a few cloud giants power so much of it.
Read Also
- Apple’s First Foldable iPhone Might Launch in 2026 – Here’s What the Leaks Say
- 16 Billion Passwords Leaked & Cock.li Email Hack: What You Need to Know Now
- Donkey Kong Bananza: Nintendo’s Bananas-Powered Switch 2 Adventure
- 2026 Nissan Leaf Reinvented as SUV with 303-Mile Range
- Tesla to Pause Model Y and Cybertruck Production at Giga Texas for One Week