From Google Cloud incidents feed. Times in Eastern (ET).
No active incidents reported by Google Cloud
Checked Nov 18, 9:19 PM EST · official feed, refreshed every 10 minutes
Google Cloud does not publish a public per-region component list; when an incident is open, its regions and services appear on the incident above.
Our 5-minute checks · last 7 days
We read Google Cloud's official status every 5 minutes. Each sliver is one hour, colored by the worst status seen; the daily figure is the share of checks with no degraded or major status. Stored since Nov 11, 9:33 PM EST.
7 days agonow
100%Wed 11/11
100%Thu 11/12
100%Fri 11/13
100%Sat 11/14
100%Sun 11/15
100%Mon 11/16
100%Tue 11/17
100%Wed 11/18
No problems flagged by our checks in this window.
Incident history
Incidents per month from the official feed, by severity. The public Google Cloud feed lists 8 incident(s) since Feb 27, 2026. History is short: dashed boxes and empty months before the feed's first entry mean no published data, not a clean record.
Last 13 weeks
OperationalMinorDegradedMajorNo data
Root causes: hack, AI, config error or something else?
For each incident in the past year we show a cause only when Google Cloud's own report states one, quoting the sentence. The category is our label for that sentence; anything else is marked Unconfirmed / not yet disclosed.
Config / deploy error: 3
Hardware / power: 2
Other (see official report): 2
Unconfirmed / not yet disclosed: 1
Oct 20, 2:00 AM EDT · resolved Oct 20, 8:08 AM EDT
Multiple services were experiencing issues in the europe-west2 region.
Hardware / power
“On Monday, 19 Oct 2026 at 22:53 US/Pacific (Tuesday, 20 Oct 2026, 06:53 BST), the primary utility provider experienced an outage on primary utility feed A, caused by an external underground cable fault on the utility network outside the data center facility.” — Google Cloud
Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.
Other (see official report)
“* The recurrence of the issue on October 9 was caused by an incomplete rollback of an upload planner feature, which broke the load balancing mechanism and overloaded a few smaller storage backend nodes.” — Google Cloud
Aug 20, 11:40 AM EDT · resolved Aug 20, 3:20 PM EDT
We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.
Config / deploy error
“Long-term engineering solutions are currently being finalized and assigned to address the root cause and strengthen system resilience regarding fiber maintenance procedures.” — Google Cloud
Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solutions (BMS) services are experiencing a service outage in europe-west4-a due to a cooling failure.
Hardware / power
“The root cause for this outage is a 3ms voltage drop in the power feed from the utility provider and subsequent utility breaker protective action.” — Google Cloud
Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss.
The big ones, with the cause in the official write-up's own words.
Jun 12, 2025
Global API outage (Service Control)
Config / deploy error
“A policy change was inserted into the regional Spanner tables that Service Control uses for policies… This policy data contained unintended blank fields… [it] exercised the code path that hit the null pointer causing the binaries to go into a crash loop.”
Impact: Google Cloud, Google Workspace and Security Operations returned 503 errors worldwide; services built on them (including Cloudflare's Workers KV) failed too.
A short playbook. Tick items as you go (saved on this device only).
1 · Confirm the impact
2 · Fail over and limit the damage
3 · Monitor and get alerts
4 · Communication templates
Customer heads-up (incident open)
Status update ({time} ET): Some of our services are slow or unavailable because of an outage at Google Cloud, a provider we use. Your data is safe. We're working around it and will update you by {next} ET. Live status: {your_status_page}
Internal alert
Google Cloud incident affecting {services} in {region} since {time} ET. Impact on us: {impact}. Owner: {name}. Failover: {yes_no}. Next check-in {next} ET.
All clear
Resolved ({time} ET): Google Cloud has recovered and our services are back to normal. If anything still looks wrong, reply here or contact {support}. Thank you for your patience.
Fill in the {curly} parts. Post updates somewhere not hosted on the affected provider.
Official links, contacts and alerts
Every link checked before publishing. Phone numbers only where Google Cloud publishes them.