Zapier Outage History

Zapier experienced an issue where links to access Zap data exports were returning errors and became temporarily inaccessible. Users were unable to access their previously generated Zap export links during this time. The incident was resolved after 10 minutes.

Zapier Agents experienced execution errors for 15 minutes (9:00-9:15 AM EST) due to a temporary connection failure. A fix was implemented and Agent runs resumed normal operation. The service was monitored for 22 minutes total to confirm full resolution.

Zapier experienced 404 errors that prevented users from editing zap templates for 1.8 hours. The engineering team investigated the root cause while the issue was classified as a minor service disruption. The incident was resolved after active investigation and troubleshooting by the technical team.

Zapier experienced intermittent delays affecting Slack-triggered Zaps starting around April 11th, causing execution delays for a small subset of workflows that use Slack as a trigger. The incident lasted 8.4 hours with the engineering team actively investigating the root cause. The issue was classified as minor and has since been resolved.

Zapier's Copilot "Ask" mode experienced a malfunction that caused repeated prompts, duplicate messages, and crashes, preventing users from building Zaps through that interface. Users were advised to use the unaffected "Build" mode as a workaround during the incident. The issue was resolved with a fix after 2.1 hours, with monitoring in place to ensure proper functionality.

Zapier experienced a 1.7-hour service incident affecting Custom Actions and Code by Zapier steps, causing services to be unavailable or experience delays. The issue initially impacted custom actions but was later discovered to also affect Code by Zapier steps. The incident was resolved after investigation into the root cause.

Zapier experienced a 35-minute service outage on April 6, 2026 (22:12-22:47 UTC) where agents failed to execute due to internal load test traffic overwhelming one of their core services. All triggered agents during this window were unable to complete their tasks. The service has been restored to normal operation and Zapier is continuing to monitor the system.

A brief spike in internal traffic caused strain on Zapier's authentication and request handling systems, resulting in failed or delayed workflow runs for customers using custom actions over a 16-minute period. The issue affected workflows that relied on these specific system paths, causing errors and slowdowns during execution. Zapier resolved the incident by addressing contributing factors, adjusting capacity, and replaying or recovering affected workflows to restore normal service operations.

Zapier experienced an issue where Functions were not executing despite triggers being received normally, starting at approximately 19:15 UTC on April 6, 2026. Users observed that Functions failed to fire and no new entries appeared in the Functions run history for affected workflows. The incident lasted 3.1 hours before normal execution was restored.

Zapier performed a PostgreSQL database upgrade from version 14 to version 17 over a 6-minute period. The upgrade was completed successfully with no customer impact identified during the maintenance window.