Zapier Outage History

Zapier's Apps component experienced partial degradation, affecting app integrations and automations for several hours. The outage began at 8:01 PM UTC and was resolved by 12:01 AM UTC.

Zapier's status page documented the progression, with the Apps component moving from Up to Partially Degraded Service and back to Up. The incident prompted two official status updates before full restoration.

Zapier experienced a brief degradation in polling-based triggers, causing delays in Zap runs that rely on polling. The outage began at Aug 21, 2025 6:36 PM UTC and was resolved by Aug 21, 2025 8:06 PM UTC, lasting roughly 1 hour 30 minutes. The Zapier status page indicated possible delays in polling triggers and that the team was investigating, with two updates issued during the incident. The incident involved the Zaps / Polling Triggers component.

Zapier experienced a brief disruption in Zap Run visibility, with some runs not appearing in Zap History immediately for roughly 50 minutes. The incident began at Aug 7, 2025 9:16 AM UTC and was resolved by Aug 7, 2025 10:06 AM UTC. The Zapier status page issued 2 updates during the incident, first acknowledging the delays and later confirming that delays were no longer occurring while monitoring continued, impacting two components: Zaps / Polling Triggers and Zaps / Instant Triggers.

Zapier experienced a brief degraded performance that delayed Google Sheets Add Row actions across Zaps / Searches & Writes. The incident began at 7:56 PM UTC and was resolved by 8:21 PM UTC, lasting about 25 minutes. The status page documented an investigation and subsequent remediation, with no data loss expected. The provider issued 2 status updates during the incident, and service returned to normal after the fix.

Zapier experienced error messages appearing in the Zap editor and on other website pages, disrupting editing workflows for users. The incident began on Jul 17, 2025 5:36 PM UTC and was resolved by Jul 23, 2025 7:11 PM UTC when the Website component returned to normal. The Zapier status page documented ongoing investigation with updates as the team worked toward a fix, and the Website component moved from degraded to normal during the incident. The outage lasted roughly 6 days and 1.5 hours, indicating a sustained disruption across the Zapier website and editor.

Zapier users faced login failures and the inability to access or manage Zaps across multiple regions. Reported symptoms included login errors, Google login failures, token request failures, and 503 responses when attempting to use Zapier services. The outage appeared global, with users in multiple regions reporting issues. The incident began around 4:41 PM UTC and persisted until around 5:54 PM UTC. StatusGator detected the issue at Jun 30, 2025 4:41 PM UTC as an Early Warning Signal ahead of any official acknowledgment.

Zapier conducted a scheduled maintenance window for a Database Upgrade Event, affecting three components: Zaps / Polling Triggers, Zaps / Instant Triggers, and Zaps / Searches & Writes. The maintenance began at 4:01 PM UTC and concluded at 5:01 PM UTC, lasting 1 hour. During this window, these components were temporarily unavailable as the upgrade progressed.

The status page posted two updates during the incident: the initial maintenance notice and a subsequent confirmation that services were restored. The affected components returned to normal operation by 5:01 PM UTC.

Zapier experienced an outage affecting Webhooks by Zapier steps in Zaps, with users seeing an error message value.replace is not a function after a recent version update. The incident began on May 20, 2025 4:51 PM UTC and was resolved by May 20, 2025 8:11 PM UTC, lasting about 3 hours and 20 minutes. The Zapier status page posted two updates during the incident, and the affected component was listed as Zaps / Searches & Writes, indicating disruptions to automations that rely on Webhooks by Zapier. Users running Zaps with Webhooks may have experienced failed steps or intermittent execution during this window.

Zapier conducted a scheduled database upgrade that required a brief maintenance window affecting the Zaps / Instant Triggers and Website components. The maintenance began at May 10, 2025 4:01 PM UTC and ended at May 10, 2025 4:31 PM UTC, lasting about 30 minutes. During this period, users may have experienced interruptions or delays when triggering automations or using the Zapier website. The status page issued two updates during the incident, describing the maintenance in progress and its completion, after which all services returned to normal.

Zapier experienced a brief outage affecting access to Zapier.com and the ability of Zaps to fire triggers. From 4:28 PM UTC to 4:30 PM UTC, users may have encountered loading issues on Zapier.com and data ingest failures that prevented some Zaps from triggering. The incident was resolved quickly, with Zapier reporting the service had recovered and operating normally, and publishing a status update at Apr 10, 2025 4:41 PM UTC to note ongoing investigation into the root cause. Affected components included Zaps / Instant Triggers, Zaps / Polling Triggers, and Website.