Zapier Partial Outage — April 19, 2026

Status: Resolved We've resolved an issue causing connection/authentication failures across Google Sheets, Google Drive, and Google Docs integrations. A recent deployment introduced a change to Google authentication fields, which led to widespread refresh/stale authentication errors. This also had an impact on Agents and MCP workflows that use these Google integrations. All impacts have been mitigated, and authentication error rates have returned to baseline. If you're still seeing issues, re-check your workflows and reconnect your Google account if prompted. We also recommend reviewing your Zap history for any gaps during the incident window, especially for high-volume or business-critical workflows. If you identify missing data, you can re-process it by replaying the affected tasks in your Zap history or using Transfer to backfill: Transfer existing data using a Zap "Transfer existing data using a Zap": https://zapier.com/help/manage/history/transfer-existing-data-using-a-zap. For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help. Affected components Agents (Operational)

Status: Resolved This issue has now been resolved, and all Zap runs should now be appearing correctly in the Zap history without delay. We apologize for the disruption and appreciate your patience as we got this resolved. If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help

Status: Resolved Resolved - We have confirmed that the issue causing a blank OAuth Authorization page on zapier.com "zapier.com": http://zapier.com and during new connection setup has been fully resolved. If you run into any issues, please reach out to us here: https://zapier.com/app/get-help Affected components Website (Operational)

Status: Resolved We’ve deployed a fix for the issue that prevented some users from adding or removing tools on Zapier MCP servers, and we’ve confirmed the issue is resolved. We apologize for the disruption and appreciate your patience as we got this resolved. If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help Affected components MCP (Operational)

Status: Resolved We’ve completed our review of the publicly reported LiteLLM package issue. Zapier was not affected. Our review confirmed that the LiteLLM versions used in our environments were not among the publicly reported impacted versions, and we found no evidence of unauthorised access or impact on customer data, Zapier systems, or services. We will continue to monitor for any new information and will share updates if anything changes. If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help.

Status: Resolved Earlier, a script error unintentionally detached saved payment methods for some active customers. This caused increased payment errors and prevented some customers from completing checkout, renewing subscriptions, upgrading plans, or paying invoices. We worked with Stripe to reattach impacted customers’ payment methods in bulk, including a final batch for any remaining affected accounts. Payment processing has resumed and our monitoring indicates payment error rates and invoice processing are back to normal. If you’re still having trouble making a payment, please contact Support: https://zapier.com/app/get-help

Status: Resolved We have successfully completed the recovery process for the intermittent task failures that occurred between March 24-26, 2026. Our team replayed all affected tasks, which have been successful with no data loss. **What Happened** Between March 24 at 11:02 AM UTC and March 26 at 2:04 PM UTC, some tasks failed for customers using Zaps that depend on our developercli service. **Resolution** We fixed the underlying issue causing this failure and completed a full replay of all impacted tasks. No action is needed on your side if affected — tasks have been automatically recovered and are now running normally. Thank you for your patience while we worked through this issue. If you do have any other questions or see any issues, please reach out to our Support team at zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components Zap History (Operational)

Status: Resolved TLDR: A production upgrade for Monolithdb from version 8.0.40 to 8.4.8 is currently resolved now and everything is functional. All systems are back to normal

Status: Resolved We’ve resolved the issue related to Zaps that were paused during a prior authentication incident. Some Zaps were automatically paused as a protective measure during an earlier incident "an earlier incident": https://status.zapier.com/incidents/01KMZFA6V1H9WP71FD7XZ8MP4A and did not automatically resume afterward. We investigated and confirmed the scope, and provided guidance directly to affected customers on how to review and restore any impacted Zaps. If you believe you may have been impacted, please review any paused Zaps and re-enable them as appropriate. And as always, Our support team is available if you have questions or need help getting workflows running again. If this is the case, or if you have any other questions please let us know at https://zapier.com/app/get-help

Status: Resolved We’ve resolved the issue causing intermittent Internal Server Errors (HTTP 500) for some Enterprise customers when editing Zaps that use app approvals. Our teams implemented a fix and confirmed recovery. If you continue to experience issues editing affected Zaps, please contact support. https://zapier.com/app/get-help Affected components Zap Editor (Operational)

Status: Resolved We’ve resolved an issue where adding certain knowledge sources in Zapier Agents could get stuck on a loading spinner. A fix has been deployed to production and verified. If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help Affected components Agents (Operational)

Status: Resolved This is now resolved. Affected components Agents (Operational)

Status: Resolved Our team has resolved the issue, and connections can now be established again.

Status: Resolved resolved Affected components Functions (Operational)

Status: Complete The maintenance is now complete. Affected components Tables (Operational)

Status: Resolved We've identified and resolved the root cause of the functions outage. The issue has been resolved and systems are operating normally. The team will continue to monitor performance and ensure full recovery across all impacted users. Affected components Functions (Operational)

Status: Resolved The incident affecting some custom action steps has been resolved. Between 22:12 and 22:47 UTC on April 6, 2026, some customers experienced failed or delayed workflow executions when using custom actions. Systems are stable and we’ve successfully replayed impacted Zap runs. Thanks for your patience.

Status: Resolved This issue has been resolved, and agent executions are operating normally. Between April 6, 2026, at 22:12 UTC and 22:47 UTC, a dependency that powers Agents became unavailable due to internal load test traffic. Agents triggered during this window may have failed to execute and will not be automatically retried. Agents that run from a Zap have been replayed and succeeded as well. If an agent run failed during this window, re-run the agent (or trigger it again via its normal trigger mechanism). New executions should now succeed. We apologize for the disruption. If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help. Affected components Agents (Operational)

Status: Resolved We've identified and resolved the soft timeout limit errors that were impacting Code by Zapier and Custom Action steps. This issue was affecting the execution and processing of these steps across multiple Zaps. All affected runs have been automatically replayed. If you experienced any issues or need additional support, please feel free to reach out at https://zapier.com/app/get-help

Status: Resolved Copilot "Ask" mode is up and running again and and can be utilized for all accounts. Earlier today the "Ask" mode was malfunctioning, causing repeated prompts, duplicate messages, and eventual crashes when users attempted to build Zaps. If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help Thank you for your patience. Affected components Copilot (Operational)

Status: Resolved We have successfully resolved the intermittent delays affecting Slack-triggered Zaps that began around Friday, April 11th. Our engineering team identified and deployed a fix, and Slack triggers are now operating as expected. If you continue to experience any delays with your Slack-triggered Zaps or have any questions, please don't hesitate to contact our support team at https://zapier.com/app/get-help We appreciate your patience while we worked through this issue.

Status: Resolved The issue causing 404 errors when editing and deleting Zap templates has been resolved. Users attempting to edit templates were encountering 404 errors due to a routing misconfiguration introduced during an ATC (Application Traffic Control) rollout, which changed the default ATC origin from the monolith to the marketing site. This broke routing for the /zap-templates path, causing edit actions to fail. The fix was deployed by completing the ATC routing correction to production. Once the rollout completed, edit functionality was restored. A remaining cosmetic bug — where the UI incorrectly indicates a template deletion failed despite the deletion succeeding — has been identified as a separate, no-impact bug and does not affect actual data. No data was lost as a result of this incident. If you're still experiencing issues, please contact Support by clicking above or visit: https://zapier.com/app/get-help Thank you for your patience.

Status: Resolved The connectivity issue which affected Zapier Agents during a 15 minute window is fully resolved. Agent executions are back to normal, and connectivity remains stable. If you have any questions, please reach out to our support team at: zapier.com/get-help. Affected components Agents (Operational)

Status: Resolved We have been able to get this issue resolved. Users should now be able to successfully download their Zap Run History export files. If you are running into any other issues, feel free to reach out to Zapier Support: https://zapier.com/app/get-help

Status: Monitoring A fix has been deployed to resolve these errors with web-scraping knowledge sources. We will continue to monitor. If you have any questions or continue to experience issues, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience. Affected components Chatbots (Degraded performance) Agents (Degraded performance)

Status: Identified Our team has identified an issue affecting Chatbot and Forms creation. Existing Forms can be edited normally. For Chatbots, users might see an error when updating the slug as well. The Engineering team is working on a fix, and we'll be updating this status page shortly once resolved. Affected components Forms (Degraded performance) Chatbots (Degraded performance)

Status: Investigating agents.zapier.com: http://agents.zapier.com/ is down and not responding. The websites are inaccessible for all users. Canvas is also not loading for users. With that said, Agent jobs appear to still be functioning as normal We are looking into the cause of this issue and will update this status as soon as possible. Affected components Agents (Degraded performance)