Is Zapier down?

Status: Investigating We're currently experiencing an issue where the Zap History page is not displaying recent Zap runs happening from today, September 9, 2026 starting at approximately 12:39PM EST. Zap runs are still processing normally, but can't be accessed or reviewed at the moment. We're actively investigating and will continue to update this status page with our progress. Many thanks for your patience! If you have any questions, please contact our Support team at: zapier.com/get-help. Affected components Zap History (Partial outage)

Status: Identified We've identified the root cause for Zap runs not displaying in the Zap History, and our Engineering team is working on a resolution. Zap runs are slowly appearing again in the Zap history, and we'll confirm once all Zap runs can be accessed. For any questions, please reach out to our Support team at: zapier.com/get-help. Affected components Zap History (Partial outage)

Status: Monitoring The Engineering team has implemented a fix for this issue, and Zap runs continue to load into the Zap History. Executions have not been affected: Zap runs are executing normally. However, the Zap run data was not rendering in the Zap history correctly. We appreciate your patience while we worked through this, and we will share a final update once all Zap runs are displaying successfully. If you have questions or need help, please contact our Support team at: zapier.com/get-help. Affected components Zap History (Partial outage)

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: Monitoring A brief infrastructure issue between approximately 8:15–9:50 AM ET caused some Zap workflows using webhook triggers to not fire, and some Zap action steps to fail. The issue has been resolved, and Zap Runs are processing normally. We're reviewing affected accounts and replaying missed webhook events where possible. If you notice a Zap that should have run during this window and did not, contact Support: zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components Instant Triggers (Degraded performance) Searches & Writes (Degraded performance)

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: Investigating Customers using Freshservice webhook triggers may not receive new updates in their Zaps. We are investigating the disruption with Freshservice and will share further information as it becomes available.

Status: Investigating We are still investigating the disruption with Freshservice and have touched base with their team to continue digging into this. We will continue to share further information as it becomes available. We appreciate your patience while our team works on this.

Status: Investigating We’re still investigating the disruption with Freshdesk. If you are experiencing issues related to this, please reach out here: https://zapier.com/app/get-help

Status: Investigating The Freshservice disruption is still under investigation. The Freshservice team has confirmed the issue and is working to implement a fix. We’ll provide the next update once we know more. If you’re experiencing this issue, please reach out to our Support team: https://zapier.com/app/get-help

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: Investigating We're currently investigating an issue affecting Tables, Chatbots, and Forms for some users. Affected users may find that existing Tables, Chatbots, or Forms are not loading and are instead being redirected to a creation page. If you need help in the meantime, contact Support: https://zapier.com/app/get-help Affected components Tables (Degraded performance) Forms (Degraded performance) Chatbots (Degraded performance)

Status: Monitoring A fix has been implemented for the issue affecting Tables, Chatbots, and Forms. These should now be loading as expected for affected users. We are continuing to monitor to confirm full stability. We will post a final update within 24 hours. If anything still seems off, contact Support: https://zapier.com/app/get-help Affected components Tables (Degraded performance) Forms (Degraded performance) Chatbots (Degraded performance)

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 Tables (Operational) Forms (Operational) Chatbots (Operational)

Status: Investigating Some customers may experience intermittent delays or failures with instant triggers, which can prevent workflows from starting. We are investigating the issue and working to restore normal processing. We will provide updates as soon as possible. Affected components Instant Triggers (Degraded performance)

Status: Investigating We're continuing to investigate a small number of workflows that failed to start between approximately 9:00–9:20 AM UTC on August 25. Affected triggers did not fire during this window. No data has been lost — failed triggers can be replayed once the issue is resolved. Our team is actively working to determine the root cause. We'll provide another update as soon as possible. If you need help: https://zapier.com/app/get-help Affected components Instant Triggers (Degraded performance)

Status: Monitoring A fix has been implemented and we are monitoring the results. We have not seen any new instant trigger failures since approximately 10:26 AM PDT (17:26 UTC). The change we deployed adds automatic retries for the failure that was preventing a small number of triggers from firing, and we are continuing to roll it out fully. No data has been lost. We have confirmed that affected triggers replay successfully, and we are now replaying the triggers that failed during this incident. Our team is monitoring closely to confirm the issue is fully resolved. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience. Affected components Instant Triggers (Degraded performance)

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)