Zapier Outage History

Zapier experienced a temporary authentication issue affecting Claude via MCP, with sign-in attempts failing or experiencing degraded login performance. The problem involved the Beta Products / MCP component and persisted from 6:36 PM UTC to 8:01 PM UTC, lasting about 1 hour 25 minutes. Users attempting to authenticate Claude through MCP during the window could have been affected.

Zapier issued two status updates on their status page during the incident, detailing the ongoing authentication problem and later confirming restoration of normal access as the MCP component returned to a healthy state. The incident was resolved by 8:01 PM UTC.

Zapier experienced a service disruption in the Beta Products / MCP component, with MCP endpoints returning 500 or 503 errors, causing some MCP tool executions to fail or be temporarily unavailable. The disruption lasted from Jan 7, 2026 9:00 AM UTC to 3:17 PM UTC UTC, and the team performed automatic restarts of the affected services to restore operation, with full recovery observed later in the day.

Zapier reported a brief Copilot-related issue affecting the Canvas integration, with Copilot not responding and errors when used within Canvas. The incident began at Jan 7, 2026 10:36 AM UTC and was resolved by Jan 7, 2026 11:11 AM UTC, lasting roughly 35 minutes. The Canvas component was briefly listed as degraded during the outage, and Zapier issued two status updates documenting the investigation and recovery.

Zapier reported an AI services disruption affecting AI-powered features such as Canvas and Beta Products / Agents. The team began investigating at Jan 5, 2026 3:51 PM UTC with the goal of restoring full functionality as quickly as possible.

The outage lasted about 4 hours and 20 minutes and was resolved by Jan 5, 2026 8:11 PM UTC. The incident prompted two status updates as engineers worked to restore the affected AI capabilities.

Zapier's Beta Products / Chatbots experienced a brief degradation that prevented chatbots from loading consistently on websites that embed Zapier chatbots. This caused intermittent loading failures and inconsistent user experiences for visitors. The outage lasted from Dec 17, 2025 10:41 AM UTC to Dec 17, 2025 11:31 AM UTC, approximately 50 minutes, and affected the Chatbots component only.

Zapier's status page documented the incident with two updates: an initial alert at Dec 17, 2025 10:41 AM UTC signaling the issue and a follow-up at Dec 17, 2025 11:31 AM UTC confirming resolution and return to normal. The issue was limited to the Beta Chatbots product; no other Zapier services were affected.

Zapier experienced an outage affecting Interfaces and Beta Products / Chatbots due to an Uploadcare incident. Users could experience issues uploading files or knowledge sources within Zapier Interfaces and Chatbots, with degraded performance. The outage began on Dec 15, 2025 8:31 PM UTC and was resolved by Dec 16, 2025 6:31 AM UTC, lasting about 10 hours. The problem stemmed from an Uploadcare incident, and Zapier is actively monitoring and working with Uploadcare to restore full functionality. The affected components were Interfaces and Beta Products / Chatbots. The status page published two updates during the incident.

Zapier experienced degraded performance for a subset of users, causing slow or failed loading of folders and Zaps. The issue affected three components: Zaps / Polling Triggers, Zaps / Instant Triggers, and Zaps / Searches & Writes. User reports described extremely slow performance and pages not loading. The incident began at 3:06 PM UTC and Zapier posted two status updates as the issue was investigated.

By 4:21 PM UTC, the services had returned to normal and the outage had lasted roughly 75 minutes. Root cause was identified and a fix was being implemented. The event appeared limited to the named Zapier components and did not represent a full platform outage.

Zapier experienced a brief partial outage affecting the Website / Support component after a third-party support platform it relies on was affected by an outage at its hosting provider. This caused delays to ticket processing and extended response times for support tasks. The incident began at 9:16 AM UTC and was resolved by 9:36 AM UTC, lasting about 20 minutes.

Status page updates showed Zapier moving from up to warn for the Website / Support component at Dec 5, 2025 9:16 AM UTC and returning to up at Dec 5, 2025 9:36 AM UTC as the issue was resolved.

Zapier experienced an outage caused by a Cloudflare network disruption that impacted several integrations, including RSS, HubSpot, and Webhooks. Hooks themselves were not directly affected, but Hooks connected to affected integrations could fail or run with delays.

The issue began around 2:55 PM UTC and a status update to warn was posted at 3:51 PM UTC, with recovery reported by 10:16 PM UTC, lasting roughly 7 hours and 21 minutes. During the incident, Zapier issued 2 status updates, and the affected component was Zaps / Instant Triggers.

Zapier experienced degraded performance with delays in triggering and running Zaps, and in Zap history. Automations may have executed slower than usual or been delayed. The issue affected three components: Searches & Writes, Polling Triggers, and Instant Triggers. The outage began on Nov 13, 2025 11:06 AM UTC and was resolved by Nov 13, 2025 1:16 PM UTC, lasting about 2 hours and 10 minutes.

Zapier’s status updates explained they were investigating delays and working to restore normal operation, with two updates posted during the incident: the first at Nov 13, 2025 11:06 AM UTC noting delays and the second at Nov 13, 2025 1:16 PM UTC confirming resolution. The impact affected automation workflows across all three components and was resolved by the time of the final update. No geographic pattern was reported; the incident was characterized as degraded triggering and history processing.