Audience Refresh Pipeline | P1 | Google Cloud Infrastructure Issue
Incident Lifecycle
Incident Timeline
Monitoring
A fix has been implemented from google and we are monitoring the results. The audience is processing the pending refreshes
May 17, 2026 at 1:55 PM UTC
Identified
We have received mitigation steps from GCP. We are working on it.
May 17, 2026 at 1:02 PM UTC
Investigating
We are still yet to hear from the GCP team. We are actively looking at the issue.
May 17, 2026 at 12:53 PM UTC
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.
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.
May 17, 2026 at 11:18 AM UTC
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 upd...
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 upd...
May 17, 2026 at 11:17 AM UTC
Was your business affected by this Zeotap outage?
Set up instant alerts for Zeotap, be the first to know about outages via email, Slack, Teams, or Discord.