Is Google Cloud down? › Outage history › Sep 1, 2026

Google Cloud partial outage on Sep 1, 2026: what happened

On Sep 1, 2026, the Google Cloud status dashboard reported "Multiple products in us-central1-b are experiencing network service degradation.". About 4 hours 10 min: from Sep 1, 2026, 14:42 UTC to Sep 1, 2026, 18:52 UTC, by the official start and resolution times.

Google Cloud right now

At our last refresh (Oct 22, 2026, 12:35 UTC) Google Cloud was up: No open incidents on the Google Cloud status dashboard.

Is Google Cloud down right now? →
Started
Sep 1, 2026, 14:42 UTC
Resolved
Sep 1, 2026, 18:52 UTC
Duration
4 hours 10 min
Official impact
Service disruption
Affected
AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Firestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud SQL, Google Compute Engine, Google Kubernetes Engine, Hybrid Connectivity, Looker (Google Cloud core), Virtual Private Cloud (VPC)
Source
Multiple products in us-central1-b are experiencing network service degradation. on the Google Cloud status dashboard

The Google Cloud status dashboard rated the impact "Service disruption": a partial outage. Some parts or some users were affected; it was not a complete outage.

What caused the Google Cloud partial outage?

"The event was triggered by the inadvertent physical disconnection of network fiber-optic cables during routine hardware maintenance. A technician was performing a scheduled capacity upgrade on data center routers that support a fraction of capacity in the us-central1-b zone and a small fraction of capacity in the us-central1-f zone."

From the Google Cloud status dashboard, incident report, Sep 10, 2026, 21:20 UTC.

When was it fixed?

The Google Cloud status dashboard marked it resolved at Sep 1, 2026, 18:52 UTC, 4 hours 10 min after it started. Its resolution note: "Addendum to Incident Report This addendum extends the Detailed Description of Impact from the previous message. Though only two clusters in a datacenter in us-central1-b and us-central1-f experienced network isolation, a few regional products with a dependency on the affected datacenter were also ..."

Timeline of official updates

Every update the Google Cloud status dashboard posted, oldest first. Times are UTC.

  1. Sep 1, 2026, 16:03 UTC service disruption

    Summary Multiple products in us-central1-b are experiencing network service degradation. Description We are experiencing a networking issue starting Tuesday, 2026-09-01 07:41 US/Pacific. The issue is affecting a portion of the us-central1-b zone. The remaining zones in the region are unaffected. Our network engineering team has put in mitigations and we are seeing services starting to recover. We will provide more information by Tuesday, 2026-09-01 09:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Customer Symptoms Customers are experiencing elevated packet loss and errors. * BigQuery * Cloud Dataflow * Cloud SQL * App Engine * Cloud Run * AlloyDB * Cloud Bigtable * Cloud Spanner * Compute Engine * Cloud VPN * Cloud Interconnect * Cloud NAT * Cloud Filestore * Cloud Hybrid Connectivity * Virtual Private Cloud * Google Kubernetes Engine * Looker (Google Cloud core) Workaround * Customers with service layer retries may see successful completions as only a portion of the zone is affected. * Customers that are severely affected and have services available in alternate zones can failover to alternate zones.

  2. Sep 1, 2026, 16:19 UTC service disruption

    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. Following network-level mitigation efforts, the underlying network infrastructure has fully recovered. Product engineering teams across Cloud are currently validating the recovery status of individual services. We will provide more information by Tuesday, 2026-09-01 10:00 US/Pacific with current details. Customer Symptoms Customers are experiencing elevated packet loss and errors. * BigQuery * Cloud Dataflow * Cloud SQL * App Engine * Cloud Run * AlloyDB * Cloud Bigtable * Cloud Spanner * Compute Engine * Cloud VPN * Cloud Interconnect * Cloud NAT * Cloud Filestore * Cloud Hybrid Connectivity * Virtual Private Cloud * Google Kubernetes Engine * Looker (Google Cloud core) * Apigee * Google SecOps SOAR Workaround * Customers with service layer retries may see successful completions as only a portion of the zone is affected. * Customers that are severely affected and have services available in alternate zones can failover to alternate zones.

  3. Sep 1, 2026, 17:09 UTC service disruption

    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 products have recovered and the engineering team is still validating a few remaining product impacts. We will provide more information by Tuesday, 2026-09-01 11:00 US/Pacific with current details. Customer Symptoms Customers are experiencing elevated packet loss and errors. * Cloud Run * App Engine Following products have recovered * BigQuery * Cloud Dataflow * Cloud Bigtable * Compute Engine * Cloud Hybrid Connectivity * Cloud Filestore * Virtual Private Cloud * Cloud Spanner * Google Kubernetes Engine * Cloud SQL * AlloyDBCloud VPN * Apigee * Cloud Interconnect * Cloud NAT * Looker (Google Cloud core) * Google SecOps SOAR * Cloud Firestore Workaround * Customers with service layer retries may see successful completions as only a portion of the zone is affected. * Customers that are severely affected and have services available in alternate zones can failover to alternate zones.

  4. Sep 1, 2026, 18:01 UTC service disruption

    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 products have recovered and the engineering team is still validating a few remaining product impacts. Routine network maintenance triggered issues in us-central1-b. We have recovered the network capacity that was impacted and restored all zonal and regional services. Maintenance in the region has been halted while proactive audits are carried out. We will provide more information by Tuesday, 2026-09-01 12:30 US/Pacific with current details. Customer Symptoms Customers are experiencing elevated packet loss and errors. * Cloud Run * App Engine Following products have recovered * BigQuery * Cloud Dataflow * Cloud Bigtable * Compute Engine * Cloud Hybrid Connectivity * Cloud Filestore * Virtual Private Cloud * Cloud Spanner * Google Kubernetes Engine * Cloud SQL * AlloyDBCloud VPN * Apigee * Cloud Interconnect * Cloud NAT * Looker (Google Cloud core) * Google SecOps SOAR * Cloud Firestore Workaround * Customers with service layer retries may see successful completions as only a portion of the zone is affected.

  5. Sep 1, 2026, 18:36 UTC service disruption

    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 products have recovered. The impacted products Cloud Run and App Engine are also seeing recovery and the errors have lowered pre-incident levels. Engineering continues to monitor and validate. Routine network fabric path maintenance triggered unexpected issues in two clusters in us-central1-b. We have recovered the network capacity that was impacted and restored all zonal and regional services. Maintenance in the region has been halted while proactive audits are carried out. We will provide more information by Tuesday, 2026-09-01 12:30 US/Pacific with current details. Customer Symptoms Customers are experiencing elevated packet loss and errors. * Cloud Run * App Engine Following products have recovered * BigQuery * Cloud Dataflow * Cloud Bigtable * Compute Engine * Cloud Hybrid Connectivity * Cloud Filestore * Virtual Private Cloud * Cloud Spanner * Google Kubernetes Engine * Cloud SQL * AlloyDBCloud VPN * Apigee * Cloud Interconnect * Cloud NAT * Looker (Google Cloud core) * Google SecOps SOAR * Cloud Firestore Workaround * Customers with service layer retries may see successful completions as only a portion of the zone is affected.

  6. Sep 1, 2026, 19:12 UTC service disruption

    Summary Multiple products in us-central1-b experienced network service degradation. Description The issue was affecting a portion of the us-central1-b zone. The remaining zones in the region were unaffected. All the impacted products have recovered. From preliminary analysis, routine network fabric path maintenance triggered unexpected issues in one cluster in us-central1-b. We have recovered the network capacity that was impacted and restored all zonal and regional services. Maintenance in the region has been halted while proactive audits are carried out. We thank you for your patience while we worked on resolving the issue. Customer Symptoms Customers experienced elevated packet loss and errors. Workaround The issue has been mitigated.

  7. Sep 29, 2026, 16:09 UTC resolved

    Addendum to Incident Report This addendum extends the Detailed Description of Impact from the previous message. Though only two clusters in a datacenter in us-central1-b and us-central1-f experienced network isolation, a few regional products with a dependency on the affected datacenter were also affected. Between 07:41 and 11:52 US/Pacific on Tuesday, September 1, 2026, the following products were affected: - Compute Engine VMs: VMs running in the affected data center lost network connectivity to resources located outside of their datacenter. From a Compute Engine perspective, this incident only affected a subset of VMs in us-central1-b and us-central1-f. - Zonal and Regional Products Based on Compute Engine Products with dependencies on VMs in the affected datacenter experienced symptoms like connection timeouts or service unavailability because the underlying VMs lost network connectivity. Examples of products that are based on Compute Engine VMs include: Apigee, Cloud SQL, AlloyDB for PostgreSQL, Dataflow, Cloud Filestore, and Looker. - Google Kubernetes Engine (GKE): GKE clusters whose control plane had dependencies on Compute Engine VMs in the affected clusters experienced errors and timeouts when administrators or nodes attempted to connect to the Kubernetes API server. Consequently, deployments might have been delayed, Kubernetes API operations might have failed, and new nodes might not have registered with the control plane (causing node pool operational delays). - Cloud Run and App Engine: Workloads in the us-central1 region experienced elevated serving latency, 5xx aborted request errors, and outbound connectivity degradation. To prevent severe request failures, traffic was diverted to other clusters. Diverting requests to other clusters temporarily caused elevated latency or errors in those clusters.Once the impacted cluster was restored, workload demand for these new backends created a 'thundering herd' of concurrent instance initializations. This sudden surge bypassed warm caches and overwhelmed internal file-serving tiers, extending symptoms until emergency capacity was provisioned. - Other Google APIs and Services, in us-central1 or a multi-region that includes us-central1, were affected if they had dependencies on software tasks in the affected clusters and weren't able to use software tasks in an unaffected cluster. Symptoms included connection timeouts or service unavailability. Examples of other Google APIs and services are: Google ...

The official incident report

Published Sep 10, 2026, 21:20 UTC. The opening of the report; the full text is on the official page.

Incident Report Summary On Tuesday, 1 September 2026, some customers in us-central1 experienced network service degradation and instance isolation for a duration of 4 hours and 11 minutes. To our customers whose businesses were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform's performance and availability. Root Cause The event was triggered by the inadvertent physical disconnection of network fiber-optic cables during routine hardware maintenance. A technician was performing a scheduled capacity upgrade on data center routers that support a fraction of capacity in the us-central1-b zone and a small fraction of capacity in the us-central1-f zone. During the hands-on maintenance, optical fibers connecting the data center routers to the network fabric were unplugged and the optical transceivers were replaced with a transceiver that supports higher-density connectivity. This transceiver was not compatible with the transceivers still in place in the data center fabric, causing a loss of connectivity for each fiber. The network is designed with redundant routers in separate data center rooms within the same building so that failure of one router does not interrupt service. The maintenance was intended to upgrade one router at a time over several days, with traffic diversions at each step and verification between steps that the network has returned to a fully-connected state. However, a procedural error in the manually orchestrated upgrade process caused the complete list of transceiver replacements across all routers to be issued to the technician without instructions to sequence the work one router at a time. The maintenance workflow ...

Read the full report on the Google Cloud status dashboard

Google Cloud partial outage questions

What caused the Google Cloud partial outage on Sep 1, 2026?

In its incident report (Sep 10, 2026, 21:20 UTC), the Google Cloud status dashboard said: "The event was triggered by the inadvertent physical disconnection of network fiber-optic cables during routine hardware maintenance. A technician was performing a scheduled capacity upgrade on data center routers that support a fraction of capacity in the us-central1-b zone and a small fraction of capacity in the us-central1-f zone."

When was the Google Cloud partial outage on Sep 1, 2026 fixed?

The Google Cloud status dashboard marked it resolved at Sep 1, 2026, 18:52 UTC, 4 hours 10 min after it started. Its resolution note: "Addendum to Incident Report This addendum extends the Detailed Description of Impact from the previous message. Though only two clusters in a datacenter in us-central1-b and us-central1-f experienced network isolation, a few regional products with a dependency on the affected datacenter were also ..."

How long did the Google Cloud partial outage last?

About 4 hours 10 min: from Sep 1, 2026, 14:42 UTC to Sep 1, 2026, 18:52 UTC, by the official start and resolution times.

Was Google Cloud completely down?

No. The Google Cloud status dashboard rated the impact "Service disruption": a partial outage. Some parts or some users were affected; it was not a complete outage. The affected parts listed were: AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Firestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud SQL, Google Compute Engine, Google Kubernetes Engine, Hybrid Connectivity, Looker (Google Cloud core), Virtual Private Cloud (VPC).

Which parts of Google Cloud were affected?

The Google Cloud status dashboard listed: AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Firestore, Cloud Run, Cloud Spanner, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud SQL, Google Compute Engine, Google Kubernetes Engine, Hybrid Connectivity, Looker (Google Cloud core), Virtual Private Cloud (VPC).

Other recent Google Cloud incidents

Full Google Cloud outage history and biggest outages → · Recent outages across all services →

Quotes are the Google Cloud status dashboard's own words, from the official incident. Is It Up or Down is independent and not affiliated with Google Cloud. Times are UTC.