Google Cloud outage shows it’s still hard to understand hyperscalers’ real resilience regimes
Google Cloud experienced a 15-hour outage due to a cooling failure in its europe-west4-a zone, affecting three services. The incident highlights the importance of understanding hyperscalers' resilience regimes and the potential for single-datacenter dependencies. The outage demonstrates that not all cloudy resilience promises are created equal, and organizations need to dig into clouds' promises of resilience.
- ▪Google Cloud's europe-west4-a zone experienced a 15-hour outage due to a cooling failure.
- ▪The outage affected three services: VMware Engine, NetApp Volumes, and Bare Metal Solutions.
- ▪The incident was caused by an electrical fault on the utility grid upstream of the datacenter.
The Register publishes from United Kingdom and files mainly under tech. We currently carry 394 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | theregister |
| Canonical URL | https://www.theregister.com/off-prem/2026/07/21/google-cloud-outage-shows-its-still-hard-to-understand-hyperscalers-real-resilience-regimes/5275405 |
| Publication time | Tue, 21 Jul 2026 07:39:30 +0200 |
| Retrieval time | 2026-07-21T06:31:42.763Z |
| Last seen | 2026-07-21T06:31:42.763Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | yBN5e7Nsx2lU |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); off prem Google Cloud outage shows it’s still hard to understand hyperscalers’ real resilience regimes Single datacenter and just three services taken down by ‘upstream’ power problem, while the rest of a zone and region kept humming Simon Sharwood Simon Sharwood APAC Editor Published tue 21 Jul 2026 // 06:39 UTC Google Cloud last week experienced an outage that analysts say demonstrates that not all promises of cloudy resilience are created equal.Google’s incident report explained that…
Excerpt limited to ~120 words for fair-use compliance. The full article is at theregister.