Zapier
Zapier is operational
User reports
What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Zapier status page.
No reviewed reports in the last 24 hours.
History
outages.live tracks Zapier since . The days before that show only what Zapier published.
Incidents in 90 days
25
Days with an incident
36
Median duration
3 h 2 min
Longest incident
6 days
Components
18Oct 22, 2026
We have not identified any customer impact or evidence of exploitation. We have completed the priority security updates and mitigations, and are closing this incident. Remaining lower-risk updates, including updates managed by our providers, will continue as follow-up work. No action is needed on your part.status.zapier.com
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). >status.zapier.com
Oct 21, 2026
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](https://zapier.com/app/get-help "support team").status.zapier.com
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](https://zapier.com/app/get-help "https://zapier.com/app/get-help")status.zapier.com
Oct 14, 2026
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](https://zapier.com/app/get-help "contact our support team"). Thank you for your patience while we resolved this issue.status.zapier.com
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](https://zapier.com/app/get-help "https://zapier.com/app/get-help").status.zapier.com
Follow Zapier
Your coding agent knows when Zapier is down, and tells you when a failure is theirs, not yours. You can also get Zapier incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "zapier" and tell me if Zapier has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=zapier/feed subscribe https://outages.live/feed.xml?providers=zapierGo from tracking outages to fixing production issues with Polylane.
Try Polylane