Independent monitoring
Google Cloud status
OperationalMerlonix has monitored Google Cloud around the clock and recorded every status change we observed. Below is a 30-day timeline of those observations and any incidents Google Cloud reported.
Snapshot as observed by Merlonix at Jul 7, 2026, 06:58 PM UTC. This is a point-in-time snapshot, not real-time — see the live vendor board for the current minute-by-minute status.
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.
Observations recorded
10
distinct status changes over 28 days we have data for
Most recent change
Jun 30, 2026
last time the observed status changed
Days by observed status
- Operational8d
- Partial outage20d
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.
Recent incidents Google Cloud reported
Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss.
majorScope: Hybrid Connectivity, Media CDN, Virtual Private Cloud (VPC)
Vertex AI Gemini API customers experienced increased error rates when accessing the global endpoint.
minorScope: Agent Assist, Dialogflow CX, Google Cloud Support, Vertex Gemini API
We are investigating elevated error rates with multiple products in us-east1
majorScope: AlloyDB for PostgreSQL, Apigee, Artifact Registry, Certificate Authority Service, Cloud Armor…
Get alerted the moment Google Cloud has a bad day.
Merlonix watches Google Cloud and your other upstreams around the clock and suppresses the false alerts they would otherwise trigger on your own sites — so you only get paged when the problem is actually yours.
Other vendors we monitor