Zapier Outage History

Zapier reported an outage affecting the MCP authentication workflow, preventing new MCP connections from being created and blocking re-authentication for existing connections. Users attempting to set up or reconnect Zapier MCP integrations encountered authentication errors.

The incident began at 5:31 PM UTC and was resolved by 12:21 AM UTC, lasting roughly 6 hours and 50 minutes. The Beta Products / MCP component was listed as degraded during the incident, and a temporary workaround involving clearing cookies for the connection app was noted. The Zapier status page issued 2 updates during the incident as the team investigated the root cause.

Zapier experienced a brief degradation affecting Interfaces, with users reporting errors when attempting to access Interfaces beginning at 6:06 PM UTC. The status page noted a Down for maintenance message for Interfaces, and the issue later expanded to include Canvas.

Zapier issued three status updates during the incident. By 6:31 PM UTC, a fix had been implemented and errors were reduced across the platform, though Canvas remained impacted. The final update at 6:41 PM UTC indicated both Interfaces and Canvas were back to normal.

Zapier's Website / Support live chat was temporarily unavailable, affecting users who rely on chat for quick help. The outage lasted about 35 minutes, beginning at 2:46 PM UTC and ending at 3:21 PM UTC. In the meantime, users could submit requests via the Get Help page to contact support by email. The incident involved two official status updates on Zapier's status page.

Zapier experienced a brief degradation in polling performance due to ongoing system updates in Zaps / Polling Triggers, resulting in delays for polling triggers for about 30 minutes. No data loss was expected, and operations remained functional beyond the delays.

The incident began at Oct 22, 2025 12:46 PM UTC and was resolved by Oct 22, 2025 2:26 PM UTC, lasting roughly 1 hour 40 minutes. The Zapier status page posted two updates during the incident: an initial note about system updates and potential delays, followed by a confirmation that normal polling had resumed. The impact was limited to Zaps / Polling Triggers with no broader Zapier service outages.

Zapier experienced a platform-wide outage caused by an upstream cloud provider, impacting a broad set of Zapier features and components. Users faced degraded or unavailable functionality across several areas, including Tables, Zaps (Polling Triggers, Searches & Writes, and Instant Triggers), Interfaces, the Zap Editor, and related website pages. The outage began at Oct 20, 2025 3:55 PM UTC and was resolved by Oct 21, 2025 2:01 AM UTC, lasting about 10 hours and 6 minutes.

Zapier experienced a brief issue where messages and links from Zapier Support were not consistently appearing in customer emails and live chat. The problem affected the Website component and could have led to missed communications for users seeking support. The incident began at Sep 30, 2025 5:56 PM UTC and was resolved by Sep 30, 2025 8:56 PM UTC.

Zapier reported a brief outage in Zaps / Polling Triggers, causing delays in triggering polling-based automation. Users relying on these Zaps may have seen actions fire later than expected or miss triggering events entirely.

The incident started at 3:21 PM UTC and was resolved by 5:11 PM UTC, lasting about 1 hour 50 minutes. The Zapier status page issued 2 updates during the incident, describing the investigation and eventual resolution, with services restored to normal after the fix. The issue appears to be isolated to the Zaps / Polling Triggers component.

Zapier.com experienced 500 errors that primarily affected the Zapier Website. The Zap Editor was inaccessible and users could not edit Zaps or switch between accounts, while Zap runs and the core Zap function remained accessible. The issue appears to be isolated to the Website component and did not disable hooks. The outage began at 12:16 AM UTC and was resolved by 2:01 AM UTC.

During the incident, the Zapier Website component moved to a warning state and two official updates were issued. The status indicated that the root cause had been identified and services returned to normal after the resolution.

Zapier experienced a partial disruption affecting Zaps / Instant Triggers, with some triggers experiencing delays while the majority continued processing normally. The incident began at Aug 29, 2025 10:56 AM UTC and was resolved by Aug 29, 2025 4:26 PM UTC, lasting about 5 hours and 30 minutes. The status page described the event as a Partial Disruption and noted that engineers were actively working on a fix, with most triggers still functioning as expected.

Zapier issued two official updates during the incident: the first acknowledged the partial disruption and ongoing investigation, and the second confirmed that the issue had been addressed and service returned toward full functionality.

Zapier experienced delays in Run processing, causing a backlog of events and slower executions in workflows that rely on event-driven triggers such as tasks and webhooks. The issue affected three components: Zaps / Searches & Writes, Zaps / Instant Triggers, and Zaps / Polling Triggers. The incident began at 4:41 PM UTC and was resolved by 9:21 PM UTC, lasting roughly 4 hours and 40 minutes. Users may have seen delays in event-triggered actions during this window.

Zapier issued 2 status updates during the incident. The root cause was addressed, but a backlog of events remained and may take up to 3 hours to catch up before overall performance returns to normal. Delays in event-triggered actions could continue briefly as processing normalized.