Zeotap Outage History
6 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Zeotap Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | GCP's Multiple services were experiencing issues in the europe-west2 region.We'd like to let you know about an incident at our cloud infrastructure provider, Google Cloud, on Tuesday, 20 October 2026. From 06:08 UTC, Google Cloud experienced an outage in its London (europe-west2) region, which… | -1707 min | Resolved |
| Jul 24, 2026 | DNS Outage — Client Services ImpactOn 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… | -1947 min | Resolved |
| Jun 10, 2026 | Scheduled Maintenance: New Audience Scheduling Feature ReleaseThe scheduled maintenance has been completed. | 40 min | Scheduled |
| May 18, 2026 | Audience Refresh — Service DisruptionThis incident has been resolved. | 79h 2m | Resolved |
| May 17, 2026 | Audience Refresh Pipeline | P1 | Google Cloud Infrastructure IssueThis incident has been resolved. | 2h 28m | Resolved |
| Dec 10, 2025 | Degraded Authentication on app.zeotap.com (Okta Outage)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… | 11 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Zeotap incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Zeotap Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Zeotap acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Zeotap outage in this window ran 3d 7h, against a mean recovery of 20h 35m. If you depend on Zeotap in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.