Zapier Outage History

Zapier experienced an issue where users encountered blank OAuth Authorization pages when trying to create new connections on the website. The problem affected the main website functionality and prevented users from establishing new integrations with third-party services. The issue was resolved after 1.7 hours when Zapier implemented a fix and restored normal OAuth authorization functionality.

Zapier experienced connection and authentication failures with Google integrations (Google Sheets, Google Drive, and Google Docs) for 9.1 hours, causing Zaps to fail, not trigger as expected, or be delayed/held. The issue has been resolved with a fix that significantly reduced authentication error rates, and Zapier is replaying any missed Zap runs that occurred during the incident. No data was lost, though some high-volume workflows may have missed runs during the outage period.

Zapier experienced delays in loading Zap History and errors on the Task Usage page, causing slow loading times for users trying to view their automation run history and usage statistics. Zap executions continued to run normally and complete as expected throughout the incident. The issue lasted 5.2 hours and was classified as a minor service disruption.

Zapier experienced a 27.7-hour incident where Zap run history displayed with delays of up to several minutes, though Zap executions continued running normally and completing as expected. The issue was caused by elevated load on the Zap history indexing system. The problem was resolved when the indexing system recovered and new Zap runs began appearing in history with normal latency.

Zapier experienced a checkout page rendering issue where payment and tax modals failed to appear correctly, preventing self-serve customers from adding or updating payment information during checkout. The incident lasted 24 minutes and affected users' ability to complete purchases. A workaround was provided allowing customers to add payment methods through the billing settings page before returning to checkout.

Zapier's Copilot feature in the Editor experienced intermittent failures for 37 minutes, with users encountering "Copilot isn't responding right now" and "Connection refused" errors. The Engineering team deployed a fix and observed a decrease in Copilot errors across the platform while continuing to monitor for normal performance restoration.

Zapier experienced degraded performance affecting customers using Zapier MCP with Claude CoWork, resulting in increased errors and non-functioning actions. The issue impacted the integration between Zapier's automation platform and Claude CoWork for approximately 2.4 hours. Zapier's engineering team investigated the problem and collaborated with Anthropic to resolve the integration issues.

Zapier experienced a 35-minute outage where users could not create new app connections using OAuth flow, encountering 404 errors or blank pages during authorization. Existing app connections remained unaffected throughout the incident. The engineering team identified and deployed a fix, with error rates declining as the resolution was implemented.

Zapier experienced an issue with several app integrations that caused trigger and action events to execute with delays or fail to execute entirely, affecting Zaps, Polling Triggers, Searches & Writes components. The engineering team implemented mitigations and optimizations to handle execution errors, restoring normal operation levels after 5.1 hours. Full functionality was restored and verified stable, with affected customers contacted regarding the resolution.

Zapier experienced a 29-hour outage where Zaps using Notion webhook-based triggers stopped firing or triggered intermittently due to Zapier not receiving webhook events from Notion between February 25-26, 2026. The issue affected all automations that relied on Notion triggers to initiate workflows. Zapier worked with Notion to identify the root cause and restore webhook delivery, with all Notion-triggered Zaps returning to normal operation.