Zapier outage history

Zapier users relying on Azure DevOps connections experienced an outage when the OAuth client secret expired (AADSTS7000222). The issue affected only Zaps using the Azure DevOps connection, specifically Zaps / Instant Triggers and Zaps / Polling Triggers, disrupting automated workflows that rely on Azure DevOps. The outage began at 12:16 PM UTC and left affected automations unable to trigger during the window.

At 12:41 PM UTC, Zapier identified the problem and began work to resolve it. An update noted that the issue was resolved for the affected connections and that manually testing the connection should restore it. By 1:21 PM UTC, Azure DevOps connections were restored and workflows relying on them were expected to operate normally again.

Users relying on Zapier Agent runs experienced intermittent 429 errors on agents.zapier.com, affecting the execution of Agent runs and related AI by Zapier executions. The issue began at 3:31 PM UTC as the status page flagged a disruption and was tied to an intermittent overload of a service powering Agent runs and AI by Zapier executions. The team planned to replay affected agent runs where possible and continued investigating the root cause. The disruption persisted for several hours and was resolved by 7:31 PM UTC as status returned to normal.

Zapier users could not view recent Zap runs in the Zap History page, while Zap executions continued to run normally. The issue affected visibility of run data rather than the processing itself and began around Sep 9, 2026 4:39 PM UTC.

Status updates progressed through a degraded display state, with engineers identifying the root cause and working toward a fix. By Sep 9, 2026 6:16 PM UTC the team had pinpointed the issue and began remediation. A fix was implemented by Sep 9, 2026 7:01 PM UTC, and Zap History began to render data again as things stabilized. The component returned to normal operation by Sep 9, 2026 7:46 PM UTC.

Zapier experienced a brief infrastructure disruption that impacted webhook triggers and some zap actions. As a result, several workflows relying on webhook triggers did not fire and certain action steps failed, affecting automation for a subset of users. The disruption occurred during the morning window, between 12:15 PM UTC and 1:50 PM UTC.

Zapier users relying on Freshservice webhook triggers experienced disrupted delivery, with Freshservice events not triggering Zapier workflows as expected. The disruption affected the Freshservice webhook integration within Zapier, interrupting automated updates and actions for affected Zaps. The disruption began at 12:06 PM UTC and persisted for several days as engineers from Zapier and Freshservice investigated and worked to identify a fix.

Zapier’s status page documented the disruption under the Freshservice - Webhook delivery disruption banner, with ongoing investigation and coordination with Freshservice. Freshservice confirmed the issue and is actively implementing a fix; the situation was still being evaluated through 7:11 PM UTC, and the service was restored by 12:46 PM UTC.

Zapier experienced a partial outage where Tables, Chatbots, and Forms failed to load for some customers, with affected pages redirecting to a creation screen. The impact began at 2:36 PM UTC and was limited to certain users and components.

A fix was implemented at 3:06 PM UTC, and engineers continued monitoring. By 3:36 PM UTC the affected features were loading normally again, marking recovery for those impacted.

Zapier experienced intermittent failures with Instant Triggers, preventing some workflows from starting and causing delays for a subset of Zaps. The impact spanned a window roughly between 9:00 AM UTC and 9:20 AM UTC UTC, with affected triggers not firing as expected. No data was lost, and failed triggers can be replayed after the issue is resolved. The incident involved Zaps / Instant Triggers components.

Zapier experienced a multi‑component disruption starting on Aug 21, 2026 9:41 AM UTC that affected Salesforce integrations and, later, ActiveCampaign app connections. Salesforce-related issues included disconnects, authentication problems, and delays or pauses for Zaps that rely on Salesforce triggers (notably polling triggers), with some connections appearing expired or disconnected in My Apps. Around the same period, customers reported 403 and 404 errors when creating or reconnecting ActiveCampaign connections, preventing new connections from being established and existing ones from functioning normally. By Aug 22, 2026 1:46 AM UTC, ActiveCampaign connections were resolved and authentication/integration began operating normally for those connections, while Salesforce investigations continued. The incident was resolved with the overall status returning to normal by 2:21 PM UTC, though follow-up checks on affected Zap runs were noted during the closure update.

A partial outage began at 11:51 PM UTC when Zapier Functions were temporarily unavailable, preventing users from creating, editing, or running Functions. Zaps and other Zapier services continued to operate, and no data loss was expected. A related issue with Sales Contact forms loading was addressed with a fix deployed around 12:01 AM UTC, and ongoing monitoring followed to confirm stability.

Later, in the afternoon and evening, users encountered errors tied to Pipedrive invalid IDs affecting triggers and actions for some Zaps. Investigations and recovery efforts continued through 4:11 PM UTC onward, with improvements noted as components moved back toward normal operation. By 7:41 PM UTC, the Website component had returned to up, signaling the broader restoration of service.

Zapier faced a series of partial outages over Aug 18–19. The Contact Sales form on Zapier's homepage failed to load starting at 5:26 PM UTC, blocking sales inquiries. A fix was deployed by 8:56 PM UTC and monitoring continued into 12:01 AM UTC as load performance improved. Separately, Zapier Functions (beta) were temporarily unavailable starting around 11:51 PM UTC, affecting the ability to create, edit, or run functions; the Functions component moved back toward normal by 12:01 AM UTC with fixes in place. Later, issues around Pipedrive IDs caused errors in certain Zaps beginning at 4:11 PM UTC and gradually recovered, with stabilization indicated by 7:41 PM UTC and the affected Zaps returning to normal.