Google Cloud

Affected: AlloyDB for PostgreSQL, Apigee, BigQuery Data Transfer Service, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Load Balancing, Cloud Memorystore, Cloud NAT, Cloud Run, Cloud Spanner, Cloud Workstations, Datastream, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud NetApp Volumes, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Looker (Google Cloud core), Google Cloud Composer, Managed Service for Apache Kafka, Memorystore for Memcached, Memorystore for Redis, Memorystore for Redis Cluster, Memorystore for Valkey, Network Connectivity Center, Persistent Disk, Private Service Connect, Speech-to-Text, Storage Transfer Service, VMWare engine, Virtual Private Cloud (VPC)

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Google Cloud:

• JFrog: JFrog Cloud Platform - Multiple Service Disruptions in GCP Europe West
• Hostinger: Hostinger Dashboard Service API Issue
• Aiven: Google Cloud VPN incident affecting services
• Grafana Cloud: Grafana Cloud unavailibity in the prod-gb-south-0 region
• Elastic Cloud: Degraded availability for some Elastic Cloud Hosted and Serverless deployments in GCP europe-west2 (London)
• Palo Alto Networks: WildFire Issue
• dbt Cloud: Delayed and stuck job runs in EMEA
• MongoDB Atlas: GCP Availability Zone europe-west2-b connectivity issues
• Sourcegraph: Sourcegraph Cloud is degraded in Europe region
• ClickHouse Cloud: Google Cloud Outage
• CockroachDB Cloud: gcp-eu-west2-b-availability-zone-issues
• Confluent Cloud: Multiple Confluent Cloud services are in a degraded state - GCP EU-West2

1. SERVICE_DISRUPTION 2026-10-20 08:35 UTC

   **Summary** Multiple services are experiencing issues in the europe-west2 region. **Description** We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT. Our engineering team continues to investigate the issue. We will...

2. SERVICE_DISRUPTION 2026-10-20 09:24 UTC

   **Summary** Multiple services are experiencing issues in the europe-west2 region. **Description** We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT. Our engineering team continues to investigate the issue. We will...

3. SERVICE_DISRUPTION 2026-10-20 11:00 UTC

   **Summary** Multiple services are experiencing issues in the europe-west2 region. **Description** We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT. Our engineering team continues to investigate the issue. We will...

4. SERVICE_DISRUPTION 2026-10-20 11:12 UTC

   **Summary** Multiple services are experiencing issues in the europe-west2 region. **Description** We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT. Due to a power event we had suffered an outage within europe-west2-b...

5. SERVICE_DISRUPTION 2026-10-20 11:58 UTC

   **Summary** Multiple services are experiencing issues in the europe-west2 region. **Description** We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT. A power event caused an outage within europe-west2-b zone. The power...

6. SERVICE_DISRUPTION 2026-10-20 12:44 UTC

   **Summary** Multiple services are experiencing issues in the europe-west2 region. **Description** We are seeing the recovery of services for most workloads in europe-west2 as of Tuesday, 2026-10-20 05:10 PDT. We will provide an update by Tuesday, 2026-10-20 07:00 PDT with...

7. AVAILABLE 2026-10-20 14:03 UTC

   **Summary** Multiple services were experiencing issues in the europe-west2 region. **Description** The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering...

Excerpts are shortened. Read the full incident on Google Cloud's status page.

Affected: Google Cloud Storage

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Google Cloud:

• Grafana Cloud: Degraded Performance with Increased Latency for Grafana Cloud Metrics and Traces in GCP US Central
• dbt Cloud: Run logs and artifacts missing for some runs (US Cell 3, GCP)
• Mixpanel: Temporary Data Ingestion Delay for US Projects
• Elastic Cloud: Delayed or Unavailable project operation in GCP us-central1
• turbopuffer: Elevated rate of 5xx in gcp-us-central1
• Temporal Cloud: Elevated GCP storage latency in us-central1 – precautionary namespace failover

1. SERVICE_DISRUPTION 2026-10-08 18:24 UTC

   **Summary** Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations **Description** We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT. Our engineering team...

2. SERVICE_DISRUPTION 2026-10-08 18:34 UTC

   **Summary** Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations **Description** We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT. Initial mitigations...

3. SERVICE_DISRUPTION 2026-10-08 18:55 UTC

   **Summary** Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations **Description** We are experiencing an issue with Google Cloud Storage beginning on Thursday, 2026-10-08 05:19 PDT. Initial mitigations...

4. SERVICE_DISRUPTION 2026-10-08 19:38 UTC

   **Summary** Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations **Description** We are continuing to mitigate the issue with Google Cloud Storage in the us-central1 region that began on Thursday,...

5. SERVICE_DISRUPTION 2026-10-08 20:48 UTC

   **Summary** Google Cloud Storage customers are experiencing elevated latencies and error rates when performing upload or write operations **Description** We are continuing to mitigate the issue with Google Cloud Storage in the us-central1 region that began on Thursday,...

6. AVAILABLE 2026-10-09 16:44 UTC

   ## Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in...

7. AVAILABLE 2026-10-14 07:15 UTC

   ## Incident Report ## Date/Time of the Issue (All time US/Pacific) **Incident First Occurrence** Incident Start: 08 October 2026 04:00 Incident End: 08 October 2026 16:30 Duration: 12 hours, 30 minutes **Incident Recurrence** Recurrence Start: 09 October 2026 04:05 Recurrence...

Excerpts are shortened. Read the full incident on Google Cloud's status page.

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)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Google Cloud:

• Weights & Biases (CoreWeave): API Degraded
• Amp: Amp unavailable due to Google Cloud incident
• Pinecone: 5xx errors on some control plane operations
• Augment Code: Major outage - Cosmos & CLI unavailable
• Elastic Cloud: Issue impacting services running in GCP us-central1
• FullStory: Multiple Fullstory Services Unavailable (NA1 Data Center)
• imgix: Increased errors for new render requests
• Sourcegraph: Cloud customers might see degraded performance because of underling Google Platform issues
• Sourcegraph: Sign-in and authentication errors
• CockroachDB Cloud: Cloud Latency, Delays, Connection Issues
• Cohere: Multiple Endpoint Disruptions
• Apollo GraphQL: Service Disruptions Due to Google Cloud Platform Issues
• Temporal Cloud: Elevated error rates in GCP us-central1
• Clerk: GCP incident in us-central1-b
• ClickHouse Cloud: Service degradation in GCP us-central-1
• Confluent Cloud: Investigating Elevated Errors in GCP us-central1
• imgix: Increased errors for new render requests
• Palo Alto Networks: URL filtering service degradation affected by GCP network service degradation
• Astronomer: Potential impact to Astro deployments in GCP us-central1

1. SERVICE_DISRUPTION 2026-09-01 16:03 UTC

   **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...

2. SERVICE_DISRUPTION 2026-09-01 16:19 UTC

   **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...

3. SERVICE_DISRUPTION 2026-09-01 17:09 UTC

   **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...

4. SERVICE_DISRUPTION 2026-09-01 18:01 UTC

   **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...

5. SERVICE_DISRUPTION 2026-09-01 18:36 UTC

   **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...

6. SERVICE_DISRUPTION 2026-09-01 19:12 UTC

   **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...

7. AVAILABLE 2026-09-03 17:47 UTC

   ## Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your environment. We are working to address the root cause and prevent this from occurring in...

8. AVAILABLE 2026-09-10 21:20 UTC

   ## 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...

9. AVAILABLE 2026-09-29 16:09 UTC

   ## 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...

Excerpts are shortened. Read the full incident on Google Cloud's status page.

Affected: AlloyDB for PostgreSQL, Apigee Edge Public Cloud, Apigee X, Artifact Registry, BigQuery Data Transfer Service, Cloud Build, Cloud Data Fusion, Cloud Filestore, Cloud Key Management Service, Cloud Monitoring, Cloud Run, Contact Center AI Platform, Dataproc Metastore, Google App Engine, Google BigQuery, Google Cloud Bigtable, Google Cloud Dataflow, Google Cloud Dataproc, Google Cloud Pub/Sub, Google Cloud SQL, Google Cloud Storage, Google Compute Engine, Google Kubernetes Engine, Identity and Access Management, Google Cloud Composer, Managed Service for Apache Kafka, Persistent Disk

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Google Cloud:

• Temporal Cloud: Customers in (GCP) us-west1 may experience elevated API latencies
• Harness: All modules are running slow in Prod1/2/3/4 due to cloud provider incident
• Render: Deployment Issues
• LangSmith: [GCP US only] LangSmith Deployments Builds Outage
• Mailgun: GCP Reporting Multi Service Outage in US-West1
• E2B: Elevated error rates for sandbox operations
• Confluent Cloud: Elevated error rates and latency in GCP us-west1
• Bugsnag: Sessions processing delays
• Palo Alto Networks: File Manager: Increased Latency in US West Region

1. SERVICE_OUTAGE 2026-08-20 16:44 UTC

   **Summary** We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region. **Description** We are experiencing an issue with multiple products, beginning on Thursday,...

2. SERVICE_OUTAGE 2026-08-20 17:13 UTC

   **Summary** We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region. **Description** Mitigation actions are implemented by our engineering teams, recovery trends...

3. SERVICE_OUTAGE 2026-08-20 17:32 UTC

   **Summary** We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region. **Description** Mitigation actions are implemented by our engineering teams, recovery trends...

4. SERVICE_OUTAGE 2026-08-20 18:03 UTC

   **Summary** The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products. **Description** Mitigation actions have been completed by our engineering teams and we are seeing recovery...

5. SERVICE_OUTAGE 2026-08-20 18:53 UTC

   **Summary** The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products. **Description** Mitigation actions have been completed by our engineering teams and we are seeing recovery...

6. SERVICE_OUTAGE 2026-08-20 19:21 UTC

   **Summary** The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated and we are working to recover all products. **Description** Mitigation actions have been completed by our engineering teams and we are seeing recovery...

7. AVAILABLE 2026-08-20 19:37 UTC

   **Summary** The issue causing timeouts, degradations, errors, and latencies across multiple us-west1 products has been mitigated. **Description** We have mitigated the issue impacting multiple products in our us-west1 region as of Thursday, 2026-08-20 10:22 PDT. Our engineering...

8. AVAILABLE 2026-08-25 06:20 UTC

   # Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business operations. Recognizing your reliance on Google Cloud, we express our sincere regrets for any operational impact experienced. Our engineering teams are actively...

9. AVAILABLE 2026-08-27 21:45 UTC

   # Incident Report ## Summary On Thursday, 20 August 2026, from 08:00 to 10:22 US/Pacific (15:00 to 17:22 UTC), multiple Google Cloud services in the us-west1 region experienced elevated latency, provisioning failures, increased error rates, and widespread service degradations...

Excerpts are shortened. Read the full incident on Google Cloud's status page.

Affected: Bare Metal Solution, Google Cloud NetApp Volumes, VMWare engine

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. SERVICE_DISRUPTION 2026-07-16 03:30 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services are experiencing temperature alerts in europe-west4-a. **Description** **GCVE:** Our engineering teams are currently working with data center facility teams to...

2. SERVICE_DISRUPTION 2026-07-16 04:17 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services are experiencing temperature alerts in europe-west4-a **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has experienced a power...

3. SERVICE_DISRUPTION 2026-07-16 04:41 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services are experiencing a service outage in europe-west4-a due to a cooling failure **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has...

4. SERVICE_DISRUPTION 2026-07-16 06:29 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services are experiencing a service outage in europe-west4-a due to a cooling failure. **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has...

5. SERVICE_DISRUPTION 2026-07-16 07:39 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services are experiencing a service outage in europe-west4-a due to a cooling failure. **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has...

6. SERVICE_DISRUPTION 2026-07-16 08:32 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services experienced a service outage in europe-west4-a due to a cooling failure. **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has...

7. SERVICE_DISRUPTION 2026-07-16 09:21 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services experienced a service outage in europe-west4-a due to a cooling failure. **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has...

8. SERVICE_DISRUPTION 2026-07-16 10:14 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services experienced a service outage in europe-west4-a due to a cooling failure. **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has...

9. SERVICE_DISRUPTION 2026-07-16 11:39 UTC

   **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services experienced a service outage in europe-west4-a due to a cooling failure. **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has...

10. SERVICE_DISRUPTION 2026-07-16 12:25 UTC

    **Summary** Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solution (BMS) services experienced a service outage in europe-west4-a due to a cooling failure. **Description** The datacenter serving europe-west4-a for GCVE, BMS, and NetApp has...

11. AVAILABLE 2026-07-18 00:22 UTC

    # Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. Please note, this information is based on our best knowledge at the time of...

12. AVAILABLE 2026-07-25 13:16 UTC

    ## \# Incident Report ## \#\# Summary On Wednesday, 15 July 2026, Google Cloud VMware Engine (GCVE), Bare Metal Solution (BMS), and Google Cloud NetApp Volumes (GCNV) experienced service interruptions for a total duration of 14 hours, 55 minutes. The root cause for this outage...

Excerpts are shortened. Read the full incident on Google Cloud's status page.

Affected: VMWare engine

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. SERVICE_DISRUPTION 2026-07-14 20:24 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. **Description** We are experiencing an issue with Google Cloud VMware Engine (GCVE) beginning Tuesday, 2026-07-14 at...

2. SERVICE_DISRUPTION 2026-07-14 21:31 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. **Description** We are experiencing an inter-site communication issue with Google Cloud VMware Engine (GCVE) stretched...

3. SERVICE_DISRUPTION 2026-07-14 22:16 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. **Description** We are experiencing an inter-site communication issue with Google Cloud VMware Engine (GCVE) stretched...

4. SERVICE_DISRUPTION 2026-07-14 23:05 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. **Description** We are experiencing an inter-site communication issue with Google Cloud VMware Engine (GCVE) stretched...

5. SERVICE_DISRUPTION 2026-07-15 00:13 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. **Description** We are experiencing an inter-site communication issue with Google Cloud VMware Engine (GCVE) stretched...

6. SERVICE_DISRUPTION 2026-07-15 01:15 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. **Description** We are experiencing an inter-site communication issue with Google Cloud VMware Engine (GCVE) stretched...

7. SERVICE_DISRUPTION 2026-07-15 01:55 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. **Description** We are experiencing an inter-site communication issue with Google Cloud VMware Engine (GCVE) stretched...

8. SERVICE_DISRUPTION 2026-07-15 03:27 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions. **Description** We are experiencing an inter-site communication issue with Google Cloud VMware Engine (GCVE) stretched...

9. AVAILABLE 2026-07-15 05:34 UTC

   **Summary** Google Cloud VMware Engine (GCVE) Stretched Cluster customers may have experienced zonal outages impacting network connectivity across multiple regions. **Description** We experienced an inter-site communication issue with Google Cloud VMware Engine (GCVE) Stretched...

10. AVAILABLE 2026-07-20 18:31 UTC

    ## Preliminary Incident Report We sincerely apologize for the disruption this incident caused to your business. We know how much you rely on Google Cloud, and we regret the impact on your productivity. We are working to address the root cause and prevent this from occurring in...

11. AVAILABLE 2026-07-24 07:10 UTC

    ## Incident Report ## Summary On Tuesday, 14 July 2026 10:00 PT, Google Cloud VMware Engine (GCVE) Stretched Cluster customers in the australia-southeast2 and europe-west3 zones experienced inter-site communication failures. The disruption was traced to a network configuration...

Excerpts are shortened. Read the full incident on Google Cloud's status page.

Affected: Hybrid Connectivity, Media CDN, Virtual Private Cloud (VPC)

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. SERVICE_DISRUPTION 2026-06-10 01:13 UTC

   **Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** A fire at a third-party data center facility required an emergency power...

2. SERVICE_DISRUPTION 2026-06-10 22:25 UTC

   **Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** A fire at a third-party data center facility required an emergency power...

3. SERVICE_DISRUPTION 2026-06-11 23:25 UTC

   **Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** A fire at a third-party data center facility required an emergency power...

4. SERVICE_DISRUPTION 2026-06-12 22:50 UTC

   **Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** A fire at a third-party data center facility required an emergency power...

5. SERVICE_DISRUPTION 2026-06-15 23:11 UTC

   **Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** A fire at a third-party data center facility required an emergency power...

6. SERVICE_DISRUPTION 2026-06-17 22:36 UTC

   **Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** Traffic rerouting from the impacted Delhi facility has caused a subset of...

7. SERVICE_DISRUPTION 2026-06-22 23:51 UTC

   **Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** Traffic rerouting from the impacted Delhi facility has caused a subset of...

8. SERVICE_DISRUPTION 2026-06-23 22:52 UTC

   **Summary** Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. **Description** Traffic rerouting from the impacted Delhi facility has caused a subset of...

9. AVAILABLE 2026-06-29 23:06 UTC

   **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 Delhi facility caused a subset of Hybrid...

Excerpts are shortened. Read the full incident on Google Cloud's status page.

Affected: Agent Assist, Dialogflow CX, Vertex Gemini API, Google Cloud Support

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. SERVICE_INFORMATION 2026-02-27 16:12 UTC

   **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 impact to...

2. AVAILABLE 2026-03-04 23:23 UTC

   # Preliminary Incident Report We apologize for the inconvenience this service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to...

3. AVAILABLE 2026-03-09 05:25 UTC

   # Incident Report ## Summary On Friday, 27 February 2026 at 04:37 US/Pacific, customers using Vertex AI Gemini API models experienced increased error rates. Impacted services included Google Cloud Support, Agent Assist, Vertex Gemini API and Dialogflow CX in US regions and the...

Excerpts are shortened. Read the full incident on Google Cloud's status page.