Google Cloud Outage History

Google Cloud experienced global connectivity and performance issues on 2025-05-16, with users worldwide reporting server timeouts, slow connections, and inability to deploy or connect to services. Reports described servers not responding and degraded performance across multiple regions, including Bogotá, Sydney, Réunion, San Francisco, and Semarang. The incident began around 07:09 UTC and was resolved by 08:00 UTC, lasting roughly 53 minutes.

StatusGator detected connectivity and performance issues starting at May 16, 2025 7:09 AM UTC, indicating an Early Warning Signal. The event appeared global in scope based on regional reports, showing widespread impact across continents. Official Google Cloud status updates are not included in the data provided.

AppSheet users worldwide experienced connectivity issues, unable to load apps, edit forms, or access linked data sources. Reports described not loading apps, inability to open editors, and upstream connect errors, with affected regions including Indonesia, India, Vietnam, New Zealand, Australia, and Canada. The disruption lasted roughly 58 minutes, from 2:46 AM UTC to 3:44 AM UTC.

StatusGator issued an Early Warning Signal at May 14, 2025 2:46 AM UTC indicating connectivity problems before Google Cloud publicly acknowledged the incident. There were no official Google Cloud status updates posted during the episode. The incident underscores how outages in AppSheet can disrupt app usage and data access for users globally.

Looker Studio dashboards were unavailable for several hours as dashboards failed to load and data retrieval from sources stalled. Users across multiple regions reported charts not rendering, widgets not loading, and data delays that hindered reporting and analysis. The issue began around 15:01 UTC and persisted until about 20:15 UTC, affecting Looker Studio users globally across the Americas and beyond.

Google Cloud AppSheet users worldwide faced an outage affecting app synchronization and access to Google Drive tables, including Google Sheets data connections. Users reported apps failing to sync, with many unable to load AppSheet apps fully and some experiencing partial loading. The incident began with an Early Warning Signal at Apr 15, 2025 8:36 AM UTC and lasted about 1 hour and 39 minutes, ending around Apr 15, 2025 10:15 AM UTC. Report volume was notably high around 09:00–09:15 UTC, with issues reported by users across multiple regions.

Status updates from Google Cloud's status page were not published during the incident. StatusGator detected the issue at Apr 15, 2025 8:36 AM UTC, as an Early Warning Signal ahead of any official acknowledgment. The outage affected AppSheet apps and their integrations with Google Drive and Google Sheets, indicating a global impact rather than a localized regional pattern.

The outage began in Google Cloud zone us-east5-c and caused connectivity issues across a broad set of services. Workloads using Google Compute Engine, Virtual Private Cloud (VPC), Cloud SQL, AlloyDB, BigQuery, Cloud Bigtable, Dataflow, Dataproc, Google Kubernetes Engine, IAM, Persistent Disk, Cloud Filestore, Cloud Firestore, Cloud Composer, and other components experienced interruptions and degraded performance. The incident was linked to a power event in the affected zone, with full recovery expected to take several hours.

AppSheet, Google's no-code app platform, experienced an outage that left many users unable to load or access AppSheet apps. The issue began around Mar 24, 2025 3:47 AM UTC and was reported by users across multiple regions, including Mexico City, Reston, Mississauga, Budapest, Hong Kong, and other locations. Reports described apps not loading or becoming unresponsive, with intermittent activity continuing through Mar 26, 2025 12:30 AM UTC. The disruption appeared global in nature, affecting a wide range of apps and workflows built on AppSheet.

An outage affected Apigee and Apigee Hybrid deployments across Google Cloud regions, causing a brief degradation in API management and traffic routing. The issue began at Mar 4, 2025 9:38 PM UTC and was resolved by Mar 4, 2025 9:45 PM UTC, lasting about 7 minutes. The degradation impacted regional API gateways and could have caused slower responses for some users while the services were in that degraded state. Google Cloud issued two official status updates during the incident, noting the degraded condition and subsequent restoration as regions returned to normal operation. The impact appeared global, affecting many regional deployments worldwide, before full recovery.

A Looker Studio outage affected users attempting to create and load reports. Users in Indonesia, India, and the United States reported slow loading and errors when generating Looker Studio reports, indicating a broader impact across multiple regions. The incident began at Mar 3, 2025 7:09 AM UTC and lasted about 58 minutes, ending at Mar 3, 2025 8:07 AM UTC.

StatusGator logged an Early Warning Signal at Mar 3, 2025 7:09 AM UTC based on user reports. There were no official Google Cloud status updates posted during the incident, suggesting the problem was isolated to Looker Studio reporting workflows rather than a broader Google Cloud outage.

Google Cloud's Cloud Asset Inventory experienced an outage that caused queries to return empty results for affected users. The issue began on Feb 19, 2025 9:14 AM UTC (01:14 US/Pacific) and persisted until Feb 20, 2025 8:00 AM UTC, when the Cloud Asset Inventory component returned to normal. During the incident, Google Cloud issued two status updates updating customers as the scope and impact were assessed. The disruption was global, affecting the Global / Cloud Asset Inventory component and potentially impacting workflows that rely on Asset Inventory queries.

The outage lasted roughly 22 hours and 46 minutes, with service restoration confirmed as the component returned to the up state.

The outage affected Google Cloud SIEM Dashboards and SOAR Advanced Dashboards for Google Security Operations (SecOps). Users attempting to view dashboards experienced loading errors and disrupted data visualizations, hampering security monitoring across multiple regional deployments of Chronicle Security and Chronicle SOAR. The issue began on Feb 18, 2025 10:42 PM UTC (14:42 US/Pacific) and lasted about 4 hours and 3 minutes, with restoration completed by Feb 19, 2025 2:45 AM UTC.