Zapier Outage History

Zapier experienced service delays and timeouts for 4.6 hours due to unusually high demand on account-related requests, causing slower responses in login functionality, delayed Zap executions, and issues with AI features. The incident affected the website, login system, and support components, with users experiencing failed actions and timeouts when accessing account information or running background tasks. Zapier identified the root cause and implemented a fix, restoring normal performance and processing of delayed trigger events.

Zapier experienced a 2-hour incident where users encountered an "Unable to verify identity. Please try again." error when attempting to transfer ownership between team members. The engineering team identified the root cause and released a fix, with monitoring in place to ensure the resolution was successful.

Zapier experienced an issue where users encountered HTTP 500 errors when trying to view upcoming invoices on the billing page, preventing access to invoice details. The problem affected the website's billing functionality for 1.4 hours. The issue was resolved after Databricks released a fix for an upstream problem, restoring normal access to invoice viewing and downloading.

Zapier's AI by Zapier service experienced 500 errors when users attempted to add knowledge sources to their AI actions. The issue affected users trying to enhance their AI automations with additional knowledge bases. The incident lasted 8.5 hours and was classified as a minor service disruption.

Zapier's chatbot service experienced a 42-minute outage where users were unable to use chat completion features due to an incorrect regional hostname configuration when accessing OpenAI's API. All user interaction attempts failed with an error message directing requests to the correct OpenAI endpoint. The engineering team investigated and resolved the connectivity issue.

Zapier experienced a 1.5-hour service incident where some customers were unable to access their chatbots, encountering "Unable to load Chatbot" errors when attempting to view or manage them. The issue was caused by an authentication problem that prevented proper chatbot loading and access. Zapier identified and resolved the authentication issue, restoring normal chatbot services while continuing to monitor system performance.

Zapier's agents.zapier.com website and Canvas feature were down and inaccessible to all users for 7.9 hours. Agent jobs continued to function normally despite the website outage. The issue was resolved by deploying a fix that restored access to both Agents and Canvas.

Zapier experienced a 44-minute issue where users encountered errors when creating new chatbots and forms, with chatbot slug updates also affected. Existing forms could still be edited normally during the incident. The engineering team resolved the issue, restoring normal creation functionality for all assets.

A third-party outage caused Zapier's chatbot users to be unable to add new web-scraped knowledge sources, while Agents provided poor responses during web browsing/scraping operations. The issues occurred during two main periods (19:18–19:35 UTC and 21:35–22:32 UTC) for a total duration of 2 hours. A fix was deployed to resolve the web-scraping errors, with existing chatbot knowledge sources remaining functional throughout the incident.

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.