Zapier Outage History

Zapier experienced an 11.9-hour outage affecting Facebook Lead Ads integrations due to an upstream issue with Meta's API, causing Zaps to fail with permission errors and preventing new leads from flowing through normally. Users experienced Zap failures and automatic pausing of their Facebook Lead Ads automations, with some leads going missing during the incident window. The issue was resolved when Facebook mitigated the API problem, and Zapier worked to replay the failed leads that occurred during the outage.

Zapier experienced a 1.2-hour incident where users encountered JavaScript errors when creating new app connections or reconnecting existing apps, displaying the message "Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'." The issue was caused by a recent code change that was subsequently identified and rolled back. The service showed signs of recovery after the rollback, with the team continuing to monitor for full resolution.

Zapier experienced high latency issues affecting hook ingestion and event processing, causing delays of approximately 30-40 minutes for some customers. The service team actively worked on a fix during the 1.1-hour incident. The issue was resolved after investigation and remediation efforts.

Zapier experienced a 2.4-hour outage affecting Google single sign-on (SSO) login functionality, preventing users from authenticating with their Google accounts. Users with existing active sessions and running automations were not impacted, and alternative login via username and password remained available. The issue was resolved by rolling back a recent website update that caused the SSO failures.

Zapier experienced an issue with error handling that caused some Zaps to be incorrectly flagged with high error ratios and automatically paused, even when they were functioning normally in actual use. Users received "High Error Ratio" emails and had their Zaps switched off despite no real performance issues. Zapier deployed a fix after 23.6 hours and advised users to manually reactivate their paused Zaps from the dashboard.

Zapier experienced an issue where users received "Session initialization failed" errors when attempting to connect apps to the platform. The incident lasted 1.8 hours and was classified as a minor service disruption. The issue was investigated and resolved, with the service returning to normal operation.

Zapier experienced errors with their Klaviyo app integration due to 522 timeout errors caused by an incident on Klaviyo's side. The integration issues affected users trying to connect Zapier with Klaviyo services for 4.9 hours. The incident was resolved by monitoring the upstream Klaviyo service disruption until it was fixed.

Between April 26-30, 2026, Zapier failed to process incoming webhooks that used non-UTF-8 character encoding (such as charset=iso-8859-1) in their Content-Type headers, causing those webhook events to be rejected instead of triggering Zaps. The issue was resolved, but affected users need to resend the failed webhooks from their upstream applications since the missed events cannot be recovered through Zapier's replay functionality.

Zapier experienced a 27-minute outage affecting agents web search and chatbot website knowledge-source syncing due to a third-party provider (Firecrawl) outage starting at approximately 4:45 AM UTC. Most affected runs recovered automatically once Firecrawl was restored, though some agent runs failed during the incident window. The service was fully restored with customers able to manually retry any failed runs through their Activity dashboard.

Zapier users experienced an issue where the Admin Center page failed to load completely, preventing access to critical user management settings including SSO, SCIM, and app connections. The Engineering team identified and applied a fix within 26 minutes. The service was restored and monitored to ensure normal operations resumed.