Zapier outage history

Status: Resolved This issue originated in an upstream incident with Salesforce's Pardot service, which caused some Pardot connections to fail when refreshing authentication. Salesforce has remediated their side, but affected connections need to be reconnected. We've deployed a fix on our side so that affected connections now show as expired. To restore your connection, reconnect your Salesforce Pardot account in Zapier. Some Zaps may have been delayed or held, and we're checking that they resume after reconnecting. If your Zaps are still failing after reconnecting, or you need help, please contact our support team: https://zapier.com/app/get-help Affected components Polling Triggers (Operational)

Status: Identified We've made good progress rolling out the security updates and are continuing to work through the remaining components while monitoring closely. We have not identified any customer impact or evidence of exploitation. We'll continue to keep you up to date as we make progress.

Status: Resolved The issue affecting real-time updates in Zapier Tables has been resolved. Collaborator changes and refreshed formula results should now appear normally. If you continue to experience issues, please contact our support team "support team": https://zapier.com/app/get-help.

Status: Resolved Our investigation into the reported PHP vulnerabilities is complete. We found no impact on Zapier services or customer data. This advisory is now closed. Security FAQ: PHP Vulnerabilities (CVE-2026-109618 and CVE-2026-109619) "1. What is this issue? Two vulnerabilities were disclosed in PHP, an open-source programming language. Both can lead to remote code execution under certain conditions. They affect PHP 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27, and 8.5 before 8.5.12. 2. Is Zapier affected? Our investigation is complete, and we found no impact on Zapier services or customer data. 3. Has customer data been affected? No. Our investigation found no impact to customer data. 4. Does this affect the Zapier WordPress integration for example? The Zapier WordPress plugin itself is not vulnerable. WordPress sites run on PHP, though, so site owners should make sure their PHP version is patched (see question 1 for the affected versions). 5. Could PHP applications I host be affected? Possibly. Applications you run yourself, including on third-party hosting platforms, may be vulnerable if they run an affected PHP version, regardless of Zapier. We recommend updating to a patched PHP version. "

Status: Resolved Our Engineering team has confirmed the service disruption at BambooHR has been resolved and the normal service has been restored. Affected Zap runs have been replayed, and no additional action is necessary. If you still have errors or have questions, please feel free to open a ticket with our Support team at https://zapier.com/app/get-help

Status: Resolved We have deployed and verified a fix for the Guided Template publishing issue. Users who require publishing approval now see Request to publish within the Guided Template flow and can successfully submit their Zap for approval instead of encountering an error. Existing approval requirements remain in place. This issue is resolved. Affected components Zap Editor (Operational)

Status: Resolved The Zoom Team Chat authentication issue has been resolved. Zoom Team Chat connections experienced authentication failures. This prevented new connections and caused Zaps using existing connections to fail or be held. Other Zoom integrations were not affected. Service has been restored. New connections are working, and existing connections are refreshing automatically. A small number of connections may still need to be reconnected manually. Thank you for your patience while we worked through this! If you need support, you can reach us at: https://zapier.com/app/get-help.

Status: Resolved The permission errors affecting shared Forms, Canvas, and Tables have been resolved, and recovery of tasks affected by this incident is complete. If you continue to experience permission errors or have questions about an affected task, please contact our support team "contact our support team": https://zapier.com/app/get-help. Thank you for your patience while we resolved this issue.

Status: Resolved We have worked with Google, and we can confirm this issue is now resolved. Files passing through Zapier worked normally during this time, and were safe to download. The file links are no longer being incorrectly flagged as a dangerous site. Thank you for your patience while we worked through this! If you need support, you can reach us at zapier.com/get-help.

Status: Resolved The issue causing duplicated query parameters on some Custom Actions and Zapier MCP requests has been resolved. Starting October 7, a deploy caused some outbound requests to include duplicate query parameters, which a subset of connected apps rejected even when inputs were valid. Not every request was affected, and standard app actions in Zaps were not impacted. A fix was deployed on October 12 at 09:40 UTC to remove the duplicated parameters, and error rates returned to normal immediately. We’ve been monitoring since and have not identified any further impact or evidence of data loss. We’re reviewing the change that introduced this to prevent similar issues going forward. If you experienced errors during this window and still need help, please reach out to our Support team at https://zapier.com/app/get-help. Affected components MCP (Operational)

Status: Resolved The issue is now considered resolved, with both Facebook and Microsoft single sign-on working as expected. If you find yourself still unable to log in, please reach out to our Support team at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help Thank you for your patience as we worked to resolve the issue. Affected components Login (Operational)

Status: Resolved This has been fully resolved. If you still face this issue, please reach out to our support team via the Get help and support with Zapie "Get help and support with Zapie": https://help.zapier.com/hc/en-us/articles/8496213764877-Get-help-and-support-with-Zapierr channels Affected components Instant Triggers (Operational) Polling Triggers (Operational)

Status: Resolved The issue intermittently affecting Agent runs and Zap runs using AI by Zapier has been resolved. The confirmed impact window goes from September 18, 2026 at 2:00am UTC to today, September 21, at 15:00 UTC. Our team continues to work with our service provider to prevent this issue in the future, implement better safeguards, and consolidate self-healing capabilities. Some Agent runs from previous days (September 18 to September 20) could not be replayed to avoid duplicate agent executions. For Agents, if you want to replay affected runs, go to your Agents dashboard: https://agents.zapier.com/bots, open the All Activity: https://agents.zapier.com/activity tab to view recent runs, and review the agent runs during the incident window. You can replay any runs that need to be reprocessed by prompting the agent in the chat to retry. For Zap runs using AI by Zapier, no action needed. Our team has successfully replayed all affected AI by Zapier runs. Many thanks for your patience while we worked through this. If you gave any questions or need help, reach out to our support team at: zapier.com/get-help. Affected components Agents (Operational)

Status: Resolved We have implemented a fix regarding Zap history runs not showing, so they should be available in your Zap history page now. If you have questions or need help, please contact our Support team at: zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help. Affected components Zap History (Operational)

Status: Resolved The issue causing some Zap workflows to not trigger from webhooks or fail on action steps between approximately 8:15–9:50 AM ET has been resolved. If you're still seeing issues with a Zap that should have run during this window, contact Support: zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components Instant Triggers (Operational) Searches & Writes (Operational)

Status: Resolved Freshservice webhook triggers are now delivering to Zapier again following a fix deployed by Freshservice. We’ve confirmed incoming webhook activity has resumed and are continuing to monitor volumes. If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help Thank you for your patience.

Status: Resolved The issue affecting Tables, Chatbots, and Forms has been resolved as of approximately 15:00 UTC. Some users were unable to load existing Tables, Chatbots, or Forms and were redirected to a creation page instead. All affected surfaces — Tables, Forms, Chatbots, and folder/subfolder creation — have been verified and are working normally. No data loss occurred, and Zap runs were not affected. If you're still experiencing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience. Affected components Forms (Operational) Chatbots (Operational) Tables (Operational)

Status: Resolved Instant trigger processing has returned to normal. We have successfully replayed the affected triggers and continue not to see any impacted Zap runs, so the incident is now resolved. If you have any questions, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help) Affected components Instant Triggers (Operational)

Status: Resolved Salesforce connections have recovered and authentication errors have returned toward normal levels. Customers should now be able to use their Salesforce integrations normally. We will continue to monitor recovery.

Status: Resolved The issue with ActiveCampaign app connections and runs returning a 403 error has been fully resolved. Authentication and integration are functioning normally again. Impacted runs during the incident period have been replayed successfully. If you're experiencing any issues, please reach out to our Support team through this link: https://zapier.com/app/get-help.