Zapier outage history

Zapier users attempting to add or reconnect Salesforce connections encountered authentication errors and 400 responses, blocking sign-in and reconnection for Salesforce integration flows. The issue began to impact multiple Salesforce integration versions, with signs of trouble appearing as early as the first status update and ongoing until a rollback was completed. Users attempting to reconnect their Salesforce accounts faced the error message Cross-org Auth flows are not supported for this external client app, preventing normal connection workflows.

Root cause tracking led to a rollback of the faulty update, and Salesforce connections were confirmed to be functional again as the rollout was reversed. By 11:36 AM UTC the rollback was in place and the team advised that you should be able to reconnect your Salesforce connections; status returned to stable at 12:31 PM UTC. For those who were automatically migrated to the latest Salesforce integration version and then attempted to reconnect, the issue affected their ability to authorize; reconnecting now should restore active connections.

Zapier reported authentication issues affecting the Close CRM integration, with some users seeing errors when connecting or reconnecting their Close accounts (for example, 'invalid_client'). This could disrupt automated tasks and data flows that rely on the integration.

The incident began at 1:36 PM UTC and was resolved by 2:46 PM UTC, lasting a little over an hour. Zapier identified the failure point and coordinated with the relevant parties to restore normal authentication. Users were advised to retry later, and if the issue persisted, to contact Zapier Support for assistance.

Zapier experienced quota-exceeded errors affecting a subset of Zap runs that rely on Google apps integrations. The issue impacted Google Drive-related actions, including Google Sheets, Google Docs, Google Slides, and Gmail actions, causing some automations to fail during the incident. The event began at 6:36 PM UTC and was resolved by 8:41 PM UTC. The Google Drive quota errors have been resolved, and the majority of affected Zap runs have been replayed as Zapier monitored error rates to ensure completion of impacted workflows.

Zapier faced two phased issues affecting BambooHR and Google Drive integrations. Beginning on 1:36 PM UTC, users could not create new BambooHR connections or test existing ones in the Zap Editor due to 403 errors, disrupting BambooHR workflow setup. An update at 8:31 PM UTC identified the root cause and indicated a fix had been released, with ongoing monitoring to confirm recovery.

On 2:21 PM UTC, engineers identified elevated errors for the Google Drive app integration, with intermittent 403 - Quota Exhausted errors across all actions. A rollback of the triggering update was implemented at 4:36 PM UTC, and by 5:51 PM UTC the overall status for Zapier moved back to up as Google Drive actions resumed functioning. Errored runs would be replayed automatically, and affected workflows began operating normally again. The BambooHR-related issue had been addressed earlier, and the Zap Editor subsequently returned to normal operation.

Translate by Zapier users encountered elevated errors beginning around 2:00 PM UTC, with 403 'User Rate Limit Exceeded' responses when attempting translations. Zapier's team identified Google Cloud Translation API v2 rate limits as the root cause and investigated ongoing elevated error rates affecting the Translate by Zapier integration. The issue spanned roughly 22 hours and was resolved by 12:36 PM UTC when translation requests returned to normal. As a result, translation tasks within automated workflows and apps using Zapier were intermittently blocked or degraded during the incident.

During the incident, automated workflows that relied on translation features could experience failures or degraded results, affecting multilingual automation and content translation steps.

Zapier conducted a scheduled infrastructure upgrade that touched Zaps / Polling Triggers. During the maintenance window, polling may have experienced delays of a few minutes as the update was applied and verified. The maintenance began at 4:06 PM UTC with Zaps remaining enabled and polling resuming automatically after the work completed.

Zapier users experienced authentication failures across multiple products, with HTTP 401 errors affecting automated workflows and integrations. The incident began at 1:36 PM UTC as the status page flagged elevated authentication problems impacting Zapier services across multiple products.

By 2:26 PM UTC a fix was applied and conditions began returning to normal across affected Zapier products and services, with ongoing monitoring. Full recovery was reported by 5:41 PM UTC when the status was updated to up, indicating the authentication issue across Zapier products had been resolved.

Some Zapier users experienced errors in AI by Zapier steps within Zaps, with DriverAdapterError reported for a subset of automations. Impact began around Jul 11, 2026 10:11 PM UTC as Zapier's status page showed an investigation into the AI by Zapier component and related steps. A fix was implemented and recovery was observed by 10:56 PM UTC, with monitoring continuing to confirm stability. Full restoration followed by 1:26 AM UTC as AI by Zapier functionality returned to normal. The incident did not constitute a platform-wide outage, and affected workflows gradually returned to normal as services stabilized.

An issue with Zapier's Airtable integration caused a partial outage, with users seeing increased 4XX errors on Zapier triggers and missed automation events. The problem began at 8:11 PM UTC and affected the Airtable connection used by Zaps. By 8:31 PM UTC, Zapier said the trigger-side impact had healed and they were looking into replaying any missed triggers.

The service returned to normal by 9:01 PM UTC, with status moving back to up.

Zapier experienced a signup-flow issue where users selecting a Team trial were unexpectedly enrolled in a Pro trial, leaving Team features unavailable during the trial period. The misrouting affected new Team trial signups and disrupted the onboarding experience for teams.

The issue began at 5:06 PM UTC and engineering teams investigated. By 10:56 PM UTC a fix had been identified and applied, with new signups now correctly receiving a Teams trial with full access to Teams features. The status returned to normal by 12:11 AM UTC.