Zapier Outage History

Zapier experienced a minor service incident where users encountered 'Cache key will cause errors if used with memcached' errors when attempting to create new connections to Facebook Lead Ads and Microsoft applications including Outlook and Teams. The issue affected the connection creation process for these specific app integrations. The incident lasted 1.2 hours and was resolved.

Zapier experienced an issue where customers creating new agents with webhook triggers or viewing agent creation pages saw placeholder URLs instead of actual webhook URLs. This affected the agent creation workflow for webhook-based automations. The issue was resolved with a deployed fix after 33 minutes of monitoring and investigation.

Zapier Agents experienced an issue where selecting certain apps as knowledge sources caused the modal to hang indefinitely with a loading spinner, preventing users from adding those sources. The problem affected customers' ability to configure knowledge sources in Zapier Agents for 1.5 hours. The root cause was identified as a recent deployment issue, and the incident was resolved by reverting that deployment.

Zapier experienced intermittent HTTP 500 Internal Server Errors for 2.4 hours that prevented some Enterprise customers from editing Zaps that use app approvals, with changes failing to save during editing. The issue was caused by the Zap editor failing to retrieve approval rules from the approvals service. Engineering teams implemented a fix and continued monitoring to ensure full resolution.

A previous incident on March 18 caused Zaps using Google Sheets and Google Drive to pause, and while that incident was resolved, some affected Zaps remained paused and were not automatically restored. Users needed to manually turn their paused Google Sheets and Google Drive Zaps back on, with the option to import any missed data using a spreadsheet transfer feature.

Zapier performed a production database upgrade of Monolithdb from version 8.0.40 to 8.4.8, which caused minor service disruptions for 47 minutes. The upgrade was completed successfully, restoring normal service functionality.

Between March 24-26, 2026, Zapier experienced intermittent task failures affecting some Zaps due to exhausted database connections in their developercli service. The issue impacted a subset of customer workflows while the majority of the platform remained operational. Zapier deployed a fix to resolve the underlying connection pool issue and initiated automatic replay of affected tasks to ensure successful completion.

Zapier experienced a 22.8-hour incident where payment methods were unintentionally removed from their systems, causing payment failures during checkout, subscription renewals, and plan changes for affected customers. Customers encountered "unable to process payment" errors and unpaid invoices due to repeated failed payment attempts. Zapier resolved the issue by reinstating payment methods and advised affected customers to re-add their payment information through billing settings as a workaround.

Zapier proactively monitored a publicly reported supply chain security issue affecting specific versions of the LiteLLM package on PyPI. After reviewing their environments, Zapier confirmed they were not using any of the affected package versions and found no evidence of impact to customer data, systems, or services. The incident was resolved through verification that no Zapier systems were vulnerable to the reported issue.

Zapier experienced issues with MCP servers where users were unable to add or remove tools, receiving messages to "switch to the account that owns the server" and getting disconnected after authentication. Users also reported the Zapier login page loading as a blank white screen, preventing access to Zaps entirely. The team identified the root cause and implemented a fix within 42 minutes.