Google Cloud Outage History

The Chronicle Security data ingestion feeds in Google Cloud experienced errors and ingestion delays beginning at 16:20 US/Pacific on 2025-01-09 (UTC start 12:20 AM UTC). The disruption affected 14 regional Chronicle Security components, resulting in degraded ingestion and delayed security telemetry across Europe, the Americas, Asia Pacific, and other regions.

Google Cloud engineers published three status updates as they investigated and worked toward recovery, with ingestion gradually returning to normal. The issue was resolved by 8:50 AM UTC, for a total duration of about 8 hours and 30 minutes.

On Jan 8, 2025 6:55 PM UTC Google Cloud reported an outage impacting Chronicle Security, with non-admin users seeing a 403 Forbidden error when signing in to the Cases view. The disruption lasted about 50 minutes, ending by 7:45 PM UTC, and affected Chronicle Security deployments across 19 regional deployments including Americas, Europe, Asia Pacific, and the Middle East.

During the incident, Google Cloud issued two official status updates describing mitigation efforts and a target resolution. A workaround was not available at the time. Services returned to normal after the issue was resolved.

Google Cloud Pub/Sub experienced an outage that affected publish and subscribe across multiple regions. Customers were unable to publish messages, and in several regions, subscribing to messages was disrupted as well. The incident began at Jan 8, 2025 4:00 PM UTC and lasted about 15 minutes, with most regions returning to normal by Jan 8, 2025 4:15 PM UTC. There was no workaround available during the incident.

The provider issued three status updates during the outage, detailing the publish issue, then the subscribe issue, and finally the recovery. By the end of the incident, regions across the Americas, Europe, Asia Pacific, Middle East, and Africa had moved to up or improving states. User reports were limited, indicating the impact was focused on Pub/Sub messaging rather than end-user services.

Google Cloud experienced issues loading data and exporting reports, affecting users trying to access data or generate exports. The incident began around 6:15 AM UTC and the Early Warning Signal was issued at Jan 8, 2025 6:18 AM UTC, with the issue resolved by Jan 8, 2025 6:49 AM UTC (about 31 minutes). Reports came in from multiple regions, suggesting a broad impact on reporting features during the window.

StatusGator detected the issue early at Jan 8, 2025 6:18 AM UTC, ahead of any official acknowledgment. There were no official Google Cloud status updates published during the event, and the affected components primarily involved data loading and report export functionality.

Google Cloud experienced an outage affecting Apigee login via SAML and intermittent Vertex Gemini API 500 errors, impacting Apigee Edge Public Cloud and Apigee X across multiple regions. Users attempting to sign into integrated developer portals and access Gemini API faced authentication failures and API errors. The outage began on 8:51 PM UTC (12:51 US/Pacific) and was resolved by 5:20 AM UTC, lasting about 8.5 hours. The incident spanned global regions with widespread impact on developer portals and API access. The Google Cloud status updates tracked the progression across affected components.

Google Cloud Console and Cloud Support experienced a brief outage affecting chat-based support. Users attempting to use chat may have faced higher latency or no responses. The incident lasted about 15 minutes, beginning on Jan 6, 2025 8:15 PM UTC and ending by 8:30 PM UTC. The outage impacted two components: Global / Google Cloud Console and Global / Google Cloud Support. The provider issued two status updates during the incident, signaling the degraded state and subsequent restoration.