Z
Outage recap · Zapier

Zapier outage — October 12, 2026

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

Errors in Custom Actions and Zapier MCP requests due to duplicated query parameters

minor
Started
Oct 12, 4:39 AM EDT
Resolved
Oct 12, 6:27 AM EDT
Duration
1h 48m

Zapier's updates (3)

  1. identified · Oct 12, 4:39 AM EDT

    We've identified an issue where some requests made through Custom Actions in Zaps or Zapier MCP include duplicated query parameters. Because of this, some customers may see errors even when their inputs are valid. Not every app or request is affected, since many apps handle duplicate query parameters without issue. Standard app actions for connected apps that run in Zaps are not affected. We'll update this page as soon as we have more information. If you need help, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").

  2. monitoring · Oct 12, 6:12 AM EDT

    A fix has been deployed that stops Custom Actions and Zapier MCP requests from sending duplicated query parameters. Error rates on affected requests dropped to normal immediately after deployment (~09:40 UTC). Not every request failed during the issue, and we have not identified evidence of data loss. If a connected app behaved unexpectedly during this window, please reach out so we can take a closer look. We’re continuing to monitor and will post a final update within 24 hours. If you need help, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help").

  3. resolved · Oct 12, 6:27 AM EDT

    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](https://zapier.com/app/get-help "https://zapier.com/app/get-help").

What our checks recorded

We checked Zapier 22 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 86 ms, against 125 ms over the 24 hours before. Zapier posted the incident at Oct 12, 4:39 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.