Critical incident

Zeotap: Audience Refresh — Service Disruption

Affected: Audience Publisher

Current status of Zeotap: Operational — live Zeotap status

Timeline

1. May 18, 2026, 07:45 UTC
   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.
2. May 18, 2026, 16:00 UTC
   identified
   Google team is actively looking at the failures.
3. May 18, 2026, 16:00 UTC
   identified
   We are continuing to work on a fix for this issue.
4. May 18, 2026, 18:26 UTC
   monitoring
   A fix has been implemented and we are monitoring the results.
5. May 19, 2026, 16:33 UTC
   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.
6. May 20, 2026, 17:25 UTC
   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.
7. May 21, 2026, 14:48 UTC
   resolved
   This incident has been resolved.

Updates as published by Zeotap (original).