Live  /  Google Cloud  /  Incident

Google Cloud: Multiple products in us-central1-b are experiencing network service degradation.

Google Cloud · cloud.google.comMinor incidentResolved2026-10-17 21:49 UTC
Public — what happened

Summary

Google Cloud said a networking problem in part of its us-central1-b zone caused increased packet loss and errors for many products, including BigQuery, Compute Engine, Cloud SQL, Google Kubernetes Engine, Cloud Run and App Engine, while other zones in the region were not affected. The company put the start at 07:41 US/Pacific on September 1, 2026, and reported that most services came back after network mitigations, with Cloud Run and App Engine the last to recover. Google Cloud said its early analysis pointed to routine network maintenance that unexpectedly caused problems in one cluster, and it paused maintenance in the region for audits. It listed the incident as ending at 11:52 US/Pacific, about 4 hours and 11 minutes in total, and said a final report would follow.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Google Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Google Cloud: paths off baseline right now, where on the route conditions change, and its full incident track record.

Included with any paid plan.

Open the Google Cloud report →

More from Google Cloud

Covered in The Squid’s Ink, Week 37, 2026, our weekly internet health report.

The full archive is on the Google Cloud status & history page.

Related: Google Cloud status & history. SquidGrid is not affiliated with Google Cloud.