Z
Outage recap · Zapier

Zapier outage — August 26, 2026

On August 26, 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.

Intermittent instant trigger failures

minor
Started
Aug 26, 12:55 PM EDT
Resolved
Aug 26, 5:41 PM EDT
Duration
4h 46m

Zapier's updates (4)

  1. investigating · Aug 26, 12:55 PM EDT

    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.

  2. investigating · Aug 26, 1:24 PM EDT

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

  3. monitoring · Aug 26, 2:59 PM EDT

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

  4. resolved · Aug 26, 5:41 PM EDT

    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 "https://zapier.com/app/get-help")]([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 58 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 190 ms, against 227 ms over the 24 hours before. Zapier posted the incident at Aug 26, 12:55 PM 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.