Zeotap Outage History

Zeotap is up right now

Zeotap had 3 outages in the last 2 years totaling 81h 42m of downtime — averaging 0.1 incidents per month.

There were 3 Zeotap outages since December 10, 2025 totaling 81h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.zeotap.com

Critical May 18, 2026

Audience Refresh — Service Disruption

Detected by Pingoru
May 18, 2026, 07:45 AM UTC
Resolved
May 21, 2026, 02:48 PM UTC
Duration
3d 7h
Affected: Audience Publisher
Timeline · 7 updates
  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 →

Major May 17, 2026

Audience Refresh Pipeline | P1 | Google Cloud Infrastructure Issue

Detected by Pingoru
May 17, 2026, 01:55 PM UTC
Resolved
May 17, 2026, 04:23 PM UTC
Duration
2h 28m
Affected: Audience Publisher
Timeline · 6 updates
  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 →

Major December 10, 2025

Degraded Authentication on app.zeotap.com (Okta Outage)

Detected by Pingoru
Dec 10, 2025, 09:08 AM UTC
Resolved
Dec 10, 2025, 09:20 AM UTC
Duration
11m
Affected: UI Services
Timeline · 4 updates
  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 →