Z
Outage recap · Zapier

Zapier outage — October 22, 2026

On October 22, 2026, Zapier had 2 reported incidents on Zapier's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Assessment of recently reported PHP vulnerabilities

none
Started
Oct 22, 10:02 AM EDT
Resolved
Oct 22, 10:46 AM EDT
Duration
44 min

Zapier's updates (2)

  1. investigating · Oct 22, 10:02 AM EDT

    We have not identified customer impact related to the PHP vulnerabilities reported on October 21, 2026. Our security and engineering teams are reviewing potential exposure **in** NodeJS services and across Zapier. The assessment is ongoing. We will share further findings here as they are confirmed. Please reach out to our [Support team](https://zapier.com/app/get-help "Support team") if you need any help in the meantime.

  2. resolved · Oct 22, 10:46 AM EDT

    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.

What our checks recorded

We checked Zapier 9 times from Zapier's start time to its resolution, once every five minutes. Every one of them reached Zapier's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 138 ms, against 142 ms over the 24 hours before. Zapier posted the incident at Oct 22, 10:02 AM EDT.

Updates are Zapier's own words from its status page (status: resolved); we never add an inferred cause.

Security updates in progress for third-party software components

none
Started
Oct 22, 11:29 AM EDT
Resolved
Oct 27, 6:56 AM EDT
Duration
115h 27m

Zapier's updates (4)

  1. investigating · Oct 22, 11:29 AM EDT

    We're applying security updates to the Node.js runtime used by parts of Zapier, following a security release from the Node.js project. We have not identified any customer impact or evidence of exploitation, and no action is needed on your part. Some updates are rolling out now, so you may see brief latency to workflows while they complete.

  2. investigating · Oct 22, 3:21 PM EDT

    We’re continuing to roll out the security updates and are monitoring the deployment closely. We have not identified any customer impact or evidence of exploitation. You may continue to see brief workflow latency while updates complete. We'll continue to keep you up to date as we make progress

  3. identified · Oct 23, 1:33 PM EDT

    _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._

  4. resolved · Oct 27, 6:56 AM EDT

    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.

What our checks recorded

We checked Zapier 576 times from Zapier's start time to its resolution, once every five minutes. Every one of them reached Zapier's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 128 ms, against 139 ms over the 24 hours before. Zapier posted the incident at Oct 22, 11:29 AM EDT.

Updates are Zapier's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Zapier. This recap summarizes incidents published on Zapier's official status page.