Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Zapier Outage History

Every past Zapier outage tracked by IsDown, with detection times, duration, and resolution details.

There were 503 Zapier outages since May 2019. The 158 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 16, 2026

April 2026: Zap Export Links Inaccessible

Detected Apr 16, 2026 4:04 PM EDT · Resolved Apr 16, 2026 4:14 PM EDT · Duration 10 minutes

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.

Minor April 16, 2026

April 2026: Temporary Agent run executions errors during a 15-minute window

Detected Apr 16, 2026 10:08 AM EDT · Resolved Apr 16, 2026 10:30 AM EDT · Duration 22 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.

Minor April 15, 2026

April 2026: 404 Errors while editing templates

Detected Apr 15, 2026 5:52 PM EDT · Resolved Apr 15, 2026 7:40 PM EDT · Duration about 2 hours

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.

Minor April 14, 2026

April 2026: Slack Triggerred Zaps: Delays in triggering

Detected Apr 14, 2026 8:50 AM EDT · Resolved Apr 14, 2026 5:12 PM EDT · Duration about 8 hours

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.

Minor April 8, 2026

April 2026: Copilots "Ask" mode is not working correctly

Detected Apr 8, 2026 1:27 PM EDT · Resolved Apr 8, 2026 3:33 PM EDT · Duration about 2 hours

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.

Minor April 8, 2026

April 2026: Errors related to Custom Actions and Code by Zapier steps

Detected Apr 8, 2026 12:08 PM EDT · Resolved Apr 8, 2026 1:48 PM EDT · Duration about 2 hours

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.

Minor April 6, 2026

April 2026: Intermittent agent execution failures

Detected Apr 6, 2026 10:10 PM EDT · Resolved Apr 6, 2026 11:34 PM EDT · Duration about 1 hour

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.

Minor April 6, 2026

April 2026: Delayed or failed custom action requests

Detected Apr 6, 2026 9:29 PM EDT · Resolved Apr 6, 2026 9:45 PM EDT · Duration 16 minutes

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.

Minor April 6, 2026

April 2026: Functions not executing

Detected Apr 6, 2026 4:12 PM EDT · Resolved Apr 6, 2026 7:17 PM EDT · Duration about 3 hours

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.

Minor April 4, 2026

April 2026: Update PostgreSQL from version 14 to 17.

Detected Apr 4, 2026 12:13 PM EDT · Resolved Apr 4, 2026 12:19 PM EDT · Duration 6 minutes

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.