Is Zeotap down?
Last checked 1m agoNo incidents right now.
Zeotap is operational right now. Last checked 1m ago; the most recent incident resolved 4d ago.
Real-time Zeotap status, recent outages, and incident history — pulled directly from Zeotap's official status page at https://status.zeotap.com every 5 minutes. Pingoru tracks 46 Zeotap services and has captured 3 incidents in the last 90 days (99.77% uptime). Get email, Slack, Discord, or webhook alerts the moment Zeotap reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Audience Publisher
Timeline · 7 updates
- 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.
- identified · May 18, 2026, 04:00 PM UTC
Google team is actively looking at the failures.
- identified · May 18, 2026, 04:00 PM UTC
We are continuing to work on a fix for this issue.
- monitoring · May 18, 2026, 06:26 PM UTC
A fix has been implemented and we are monitoring the results.
- 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.
- 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.
- resolved · May 21, 2026, 02:48 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Audience Publisher
Timeline · 6 updates
- 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
- 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.
- 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.
- identified · May 17, 2026, 01:02 PM UTC
We have received mitigation steps from GCP. We are working on it.
- 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
- resolved · May 17, 2026, 04:23 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Started May 18, 2026, 07:45 AM UTC · Resolved May 21, 2026, 02:48 PM UTC · 3d 7h
- Started May 17, 2026, 01:55 PM UTC · Resolved May 17, 2026, 04:23 PM UTC · 2h 28m