Is Zeotap Down?

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.

This incident has been resolved. --- [2026-05-20T17:25:45.363Z] (monitoring) 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. --- [2026-05-19T16:35:12.944Z] (monitoring) 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. --- [2026-05-18T18:26:40.175Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-05-18T16:00:59.323Z] (identified) We are continuing to work on a fix for this issue. --- [2026-05-18T16:00:52.840Z] (identified) Google team is actively looking at the failures. --- [2026-05-18T07:45:33.141Z] (investigating) 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.

This incident has been resolved. --- [2026-05-17T13:56:41.153Z] (monitoring) A fix has been implemented from google and we are monitoring the results. The audience is processing the pending refreshes --- [2026-05-17T13:02:44.597Z] (identified) We have received mitigation steps from GCP. We are working on it. --- [2026-05-17T12:53:45.739Z] (investigating) We are still yet to hear from the GCP team. We are actively looking at the issue. --- [2026-05-17T11:18:49.929Z] (investigating) ⏺ 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. --- [2026-05-17T11:17:38.182Z] (investigating) 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