Zeotap Outage History

Started Oct 20, 2026, 12:30 AM UTC· resolved Oct 20, 2026, 06:05 AM UTC

1. resolved Oct 21, 2026, 10:32 AM UTC

   We'd like to let you know about an incident at our cloud infrastructure provider, Google Cloud, on Tuesday, 20 October 2026. From 06:08 UTC, Google Cloud experienced an outage in its London (europe-west2) region, which caused errors and network disruption across several Google Cloud services. Google reported that the incident was mitigated at 14:00 UTC the same day. Details are available on Google's status page: https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj During this time, some Zeotap services that rely on the affected Google Cloud services saw delays in real-time data processing, which may also have delayed related activations such as journeys. Some requests to services hosted in the affected region may have returned errors for part of this period. As Google restored its services, Zeotap services recovered and have been operating normally since. Our team monitored closely throughout the incident and recovery, and is reviewing all affected processing to make sure it has completed. If anything needs your attention, we will contact you directly. We will continue to monitor until Google publishes its final incident analysis. If you notice anything unexpected in your data from 20 October, please reply to this email or raise a support ticket and we'll look into it straight away. We apologise for any inconvenience this may have caused.

Read the full incident report →

Started Jul 23, 2026, 12:00 AM UTC· resolved Jul 23, 2026, 03:30 AM UTC

1. resolved Jul 24, 2026, 08:27 AM UTC

   On 23 July 2026, between approximately 06:00 and 11:00 IST, a DNS resolution issue disrupted several Client Services. Impact was intermittent and varied by service as DNS caches expired and refreshed, with the most noticeable disruption for most services around 09:00 IST. During this window some clients may have seen errors or elevated latency when accessing affected services. The issue has since been fully resolved and all services are operating normally. We apologise for any inconvenience caused.

Read the full incident report →

Started May 18, 2026, 07:45 AM UTC· resolved May 21, 2026, 02:48 PM UTC

1. investigating May 18, 2026, 07:45 AM UTC

   We are currently experiencing a disruption to our Audience Refresh and Export pipeline. Audience segment refresh and export jobs are failing or significantly delayed. The issue has been traced to an infrastructure-level problem on Google Cloud's side affecting our EU region. Google Cloud engineering is actively investigating and working on a fix. Impact: Audience segments may not refresh on schedule. Manually triggered jobs may also fail. No customer data has been lost and all segment configurations remain intact. We are monitoring the situation closely and are in active contact with Google Cloud support.

2. identified May 18, 2026, 04:00 PM UTC

   Google team is actively looking at the failures.

3. identified May 18, 2026, 04:00 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring May 18, 2026, 06:26 PM UTC

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

5. monitoring May 19, 2026, 04:33 PM UTC

   Mitigation measures implemented by Zeotap and Google Cloud continue to be monitored closely. While several previously impacted jobs have recovered successfully, we are still observing intermittent instability affecting parts of the Audience Refresh and Export workflows. As a result, some audience refreshes and downstream exports may continue to experience delays or failures while Google Cloud continues investigating the underlying infrastructure issue. No customer data has been lost, and all audience definitions and configurations remain intact.

6. monitoring May 20, 2026, 05:25 PM UTC

   Following our previous updates, the underlying Google Cloud infrastructure issue continues to impact parts of the Audience Refresh and Export workflows. Zeotap continues to take the required mitigation steps from our side, including re-triggering affected audience jobs and working to unblock delayed processing. Some jobs may still experience delays or failures while the Google-side issue remains under investigation. We are monitoring the situation closely and are in active contact with Google Cloud support.

7. resolved May 21, 2026, 02:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 17, 2026, 11:17 AM UTC· resolved May 17, 2026, 04:23 PM UTC

1. investigating May 17, 2026, 11:17 AM UTC

   2026-05-17 06:00 UTC We are aware of an issue affecting Audience Segment Refresh and Export for some customers. Segments that were scheduled to refresh or were manually triggered after 06:00 UTC today may be delayed or show a failed status. Our team is actively investigating. We have identified this as an issue with our cloud infrastructure provider, who has confirmed they are working on a fix. No customer data has been lost. All segment definitions and configurations remain intact. Next update: 12:00 UTC

2. investigating May 17, 2026, 11:18 AM UTC

   ⏺ Update — 2026-05-17 11:30 UTC We have taken remediation steps on our side and our cloud provider (Google Cloud) has confirmed an infrastructure issue affecting a subset of compute instances in our EU region. Their team is actively working on resolution. Audience Refresh and Export jobs triggered during this window may show as failed. Once resolved, we will re-trigger affected jobs and no action will be required from customers. Next update: 12:00 UTC or sooner if status changes.

3. investigating May 17, 2026, 12:53 PM UTC

   We are still yet to hear from the GCP team. We are actively looking at the issue.

4. identified May 17, 2026, 01:02 PM UTC

   We have received mitigation steps from GCP. We are working on it.

5. monitoring May 17, 2026, 01:55 PM UTC

   A fix has been implemented from google and we are monitoring the results. The audience is processing the pending refreshes

6. resolved May 17, 2026, 04:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 10, 2025, 09:08 AM UTC· resolved Dec 10, 2025, 09:20 AM UTC

1. investigating Dec 10, 2025, 09:08 AM UTC

   We are currently investigating an issue where some users are unable to log in to app.zeotap.com or are seeing errors during authentication. Our engineering team is analyzing the issue and we will provide an update as soon as we have more information.

2. identified Dec 10, 2025, 09:09 AM UTC

   Identified – Third-party (Okta) This is impacting login flows to app.zeotap.com, including new sign-ins and session renewals. Our systems remain up and healthy, but users may not be able to authenticate successfully until Okta restores service. We are closely monitoring Okta’s status and will share further updates as they become available.

3. monitoring Dec 10, 2025, 09:17 AM UTC

   Okta has reported recovery of their services and we are seeing successful logins to app.zeotap.com again. We are monitoring authentication error rates and performance to ensure everything remains stable before marking this incident as resolved.

4. resolved Dec 10, 2025, 09:20 AM UTC

   This incident has been resolved. The login issues on app.zeotap.com were caused by an outage at our identity provider (Okta), which prevented some users from authenticating. There was no impact to stored data or running workloads; only authentication flows were affected. We will continue to work with our provider to reduce the risk of similar issues in the future.

Read the full incident report →

Started Jun 12, 2025, 07:16 PM UTC· resolved Jun 12, 2025, 10:31 PM UTC

1. investigating Jun 12, 2025, 07:16 PM UTC

   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

2. investigating Jun 12, 2025, 07:41 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 12, 2025, 09:02 PM UTC

   Google's engineers have identified the root cause and have applied appropriate mitigations. We continue to monitor.

4. resolved Jun 12, 2025, 10:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 15, 2025, 12:00 PM UTC· resolved May 15, 2025, 12:30 PM UTC

1. resolved May 16, 2025, 07:29 AM UTC

   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.

2. postmortem May 16, 2025, 07:32 AM UTC

   **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.

Read the full incident report →