Is Zeotap Down Right Now? Discover if there is an ongoing service outage.

Google has confirmed an Identity & Access Management service issue that is cascading across several products. Error rates and time-outs are occurring for workloads running in **europe-west1, west2, west3, west4, west6, west8, west9, west10 and west12**. We are currently. investigating the issue. #### Impacted GCP products Cloud Data Fusion · Cloud Memorystore (Redis & Memcached) · Cloud Shell · Cloud Workstations · Cloud Bigtable · Cloud Dataproc · Cloud Storage · Identity & Access Management · plus ancillary services flagged by Google. #### Customer impact Applications or batch jobs that rely on the above services **may experience 5xx errors, authentication failures, or complete unavailability**. Multi-region fail-over traffic remains healthy. More Update on: https://status.cloud.google.com/index.html

**Incident window \(IST\)** 15 May 2025 — 11:59 to 12:26 UTC \(≈ 27 minutes\) **Service impacted** [app.zeotap.com](http://app.zeotap.com) dashboards and APIs \(partial outage, global\) #### **What happened** A newly-deployed Cloudflare rule—meant to route a specific marketing-widget path to a new backend—was too broadly scoped. Legitimate UI traffic was unintentionally rewritten and forwarded to an inactive origin, resulting in 4xx/5xx errors. #### **Customer impact** * UI pages failed to load certain resources, leading to blank or error states. * Approx. 2 k requests returned errors during the 27-minute window #### **Root cause** A logical grouping mistake in the rule’s filter \(AND / OR precedence\) caused it to match all requests that contained particular referrer domains, regardless of host or path. #### **Immediate remediation** * 12:26 — Rule disabled and cache purged. * Error rates returned to normal within seconds. #### **Preventive actions** 1. **Safer change process** – Cloudflare rules will move to Infrastructure-as-Code with mandatory peer review. 2. **Staged roll-outs** – Future edge-rules will deploy first to a staging zone and a limited canary cohort. 3. **Faster detection** – Synthetic checks for critical UI paths will alert after three consecutive failures \(≈ 3 min\). We apologise for the disruption and appreciate your patience while we improve our safeguards.

Between 12:03 UTC and 12:28 UTC we saw an elevated API error rate (peaking at ≈ 7 %). The underlying issue has been fixed and the platform is operating normally. We are monitoring closely.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.