Zapier Outage History

Zapier reported a partial outage affecting several app integrations, resulting in delayed triggers and sporadic delays for some actions. The issue impacted Zaps / Polling Triggers and Zaps / Searches & Writes, causing automations to run late or not at all. The outage began at Feb 26, 2026 5:26 PM UTC and was resolved by Feb 26, 2026 6:51 PM UTC, lasting about 1 hour and 25 minutes. The provider issued 2 official status updates during the incident as engineers investigated and implemented mitigations.

Zapier experienced a brief issue affecting the Change History display in the Editor on the Zapier Website. Users could not view past edits in the left editor sidebar, potentially impacting version tracking during editing sessions. The incident began at Feb 12, 2026 6:06 PM UTC and was resolved by Feb 12, 2026 6:21 PM UTC, with the Website component returning to normal after about 15 minutes.

Zapier experienced a brief degradation in its AI features, impacting Beta Products for Chatbots and AI Agents. Users reported chatbots failing when adding or using table-based knowledge sources, with on-screen errors in some cases. AI Agents also faced trouble loading new data sources, and runs that rely on existing knowledge sources could be intermittent, with some runs succeeding while others failed. The outage began at Feb 12, 2026 3:42 PM UTC and was resolved by Feb 12, 2026 5:56 PM UTC, lasting about 2 hours and 14 minutes. The incident impacted 2 components: Beta Products / Chatbots and Beta Products / Agents.

Zapier documented the incident on its status page with two updates, noting investigation and subsequent restoration. A temporary workaround was put in place while the issue was addressed, and both affected components returned to normal operation by the end of the incident.

Zapier experienced an OAuth login outage affecting the MCP component, impacting new customers attempting to sign in to the MCP agent platform. New customers who signed up after 6:00 PM UTC UTC may have encountered OAuth login failures when accessing MCP; other Zapier services remained available.

Per Zapier status updates, the MCP issue was listed as degraded at 3:31 PM UTC and resolved by 8:31 PM UTC, a duration of about 5 hours. The MCP component had 2 official updates during the incident. The current updates indicate the root cause is under investigation and appears related to a recent change affecting the OAuth login flow for MCP.

The Zapier parser backend service experienced a brief disruption that could prevent access to mailboxes and delay processing of inbound emails. The outage began at Jan 22, 2026 8:36 PM UTC and was resolved by Jan 22, 2026 9:36 PM UTC, lasting roughly 1 hour. The issue was associated with the Zaps / Instant Triggers component, tied to the parser service behind mailbox features.

During the incident, Zapier posted two status updates describing the disruption and its resolution as the parser service recovered.

Zapier experienced a brief degradation in the Agent Templates functionality within the Beta Products / Agents area, with errors returned as 'Something went wrong while trying to use this template.' The issue began at 2:57 PM UTC and was resolved by 4:51 PM UTC, lasting roughly 1 hour and 54 minutes. The Zapier status page issued two updates during the incident, detailing the investigation and restoration of the affected templates. The disruption appeared isolated to the Beta Agents component, with other parts of the platform unaffected.

Zapier users attempting to create new Zaps via the Forms Actions panel encountered errors that prevented creation through that flow. Existing Zaps and other methods for creating Zaps remained functional. The issue began on 7:31 PM UTC and prompted a support investigation into the Forms Actions panel flow. A workaround was provided: you can create a new Zap manually from the dashboard, but use the "Form Submission Created..." option. By 8:56 PM UTC, the issue was resolved and the Forms Actions panel returned to normal operation. The incident involved two status updates and lasted about 1 hour 25 minutes.

Zapier experienced a brief timeout affecting Zapier Tables and some frontend services tied to Tables. The incident occurred over a roughly 3-minute window from 4:50 PM UTC to 4:53 PM UTC UTC (11:50 AM–11:53 AM ET). Some Zap runs were placed on hold and access to Tables and related components may have been momentarily disrupted during this period. The issue was resolved with normal functionality restored shortly after.

Zapier experienced a brief degraded performance in the App Directory, with some app images not rendering and instead showing broken image icons on zapier.com/apps. The issue affected the Website component and was visible to users browsing the App Directory. The outage lasted roughly 10 minutes, with the status transitioning from up to warn and then back to up as the team investigated and resolved the problem. The incident began at 5:31 PM UTC and was resolved by 5:41 PM UTC.

Zapier reported a partial outage impacting the Interfaces component, with some Zap runs returning deprecation errors due to a deprecated API endpoint. This disrupted workflows that rely on Zapier Interfaces. The incident prompted investigations and two official updates as engineers worked to resolve the issue. The Interfaces component transitioned from degraded to normal as the fix was applied.