Independent monitoring

Google Cloud status

Operational

Merlonix has monitored Google Cloud around the clock and recorded every status change we observed. Below is a 30-day timeline of those observations, followed by incident and maintenance details from the latest recorded snapshot.

Snapshot as observed by Merlonix at Oct 17, 2026, 08:31 AM UTC. This is a point-in-time snapshot, not real-time — see the live vendor board for the current minute-by-minute status.

Independent monitoring by Merlonix. Not affiliated with, endorsed by, or an official status page of Google Cloud. All observations are Merlonix’s own, sampled independently from Google Cloud’s published status source. Google Cloud is a trademark of its respective owner and is named here only to describe what we monitor.

We’ve recorded only 7 status observations for Google Cloud so far — not yet enough history to publish a full, dependable 30-day record. The timeline below shows what we have; treat it as preliminary.

30-day observation timeline

Each cell is one UTC day, coloured by the most severe status we observed that day. A “degraded” day reflects Google Cloud’s own published component-level status and may mean a single component was affected while the overall service was fine.

OperationalDegradedPartial outageMajor outageMaintenanceNo data

Observations recorded

distinct status changes over 19 days we have data for

Most recent change

Oct 14, 2026

last time the observed status changed

Days by observed status

Operational18d
Partial outage1d

What Merlonix monitors for Google Cloud

Merlonix polls Google Cloud's published status source around the clock and records every change we observe — overall status, component-level incidents, and their start/resolve times. The timeline and incidents below are Merlonix's own observations, sampled independently of Google Cloud.

Incidents and maintenance in the latest snapshot

Entries from Google Cloud’s latest recorded status snapshot may include active incidents, resolved notices or scheduled maintenance.

Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.
major
Scope: Google Cloud Storage
resolvedsince Oct 8, 2026Google Cloud source ↗
Multiple products in us-central1-b are experiencing network service degradation.
major
Scope: AlloyDB for PostgreSQL, Apigee, Cloud Filestore, Cloud Run, Cloud Spanner…
resolvedsince Sep 1, 2026Google Cloud source ↗
We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.
critical
Scope: AlloyDB for PostgreSQL, Apigee Edge Public Cloud, Apigee X, Artifact Registry, BigQuery Data Transfer Service…
resolvedsince Aug 20, 2026Google Cloud source ↗
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.
major
Scope: Bare Metal Solution, Google Cloud NetApp Volumes, VMWare engine
resolvedsince Jul 15, 2026Google Cloud source ↗
Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.
major
Scope: VMWare engine
resolvedsince Jul 14, 2026Google Cloud source ↗

For incident counts and recent examples across the historical window, read the 30-day vendor status digest. The digest has its own dated snapshot and counts scheduled maintenance separately.

Reduce alert noise during Google Cloud incidents.

When a monitored asset has Google Cloud listed as a dependency, Merlonix suppresses its alert notifications while the vendor reports degradation or an outage. The alert stays visible in your dashboard.

Start free for 14 days Or start free — $0, no card

How vendor-aware alerting works →

Other vendors we monitor

Amazon Web Services Anthropic Cloudflare GitHub Microsoft Azure OpenAI All vendor status →