Z
Outage recap · Zapier

Zapier outage — September 1, 2026

On September 1, 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.

Freshservice - Webhook delivery disruption

none
Started
Sep 1, 8:03 AM EDT
Resolved
Sep 7, 8:44 AM EDT
Duration
144h 41m

Zapier's updates (5)

  1. investigating · Sep 1, 8:03 AM EDT

    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.

  2. investigating · Sep 3, 10:16 AM EDT

    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.

  3. investigating · Sep 3, 5:39 PM EDT

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

  4. investigating · Sep 4, 3:08 PM EDT

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

  5. resolved · Sep 7, 8:44 AM EDT

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

What our checks recorded

We checked Zapier 576 times from Zapier's start time to its resolution, once every five minutes. Our request could not reach Zapier on 1 of those checks. Median response time was 175 ms, against 147 ms over the 24 hours before. Zapier posted the incident at Sep 1, 8:03 AM EDT; our checks first failed 677 minutes later.

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.