Zapier favicon

Zapier outage on 2026-11-03

zapier.com
November 2026 3 Minor incident

Zapier's template recommendations and template setup broke for 37 minutes on 3 November 2026. The fault sat on Zapier's side, inside the homepage template flow, not in any workflow you had already built.

Started

21:03 UTC

Duration

Lasted 37m

Source

IsDown

Next time

Zapier is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

Zapier logged one incident this day, starting at 21:03 UTC and lasting 37 minutes. The incident title is "Delayed or failed template recommendations and template setup". Zapier's own update says the trouble actually began around 20:00 UTC, before the incident was opened, with some users seeing slow loading or errors on template recommendations on the Zapier homepage. The same update says Zapier was also investigating reports that clicking "Try it" on a template could hang or return "Something went wrong while trying to use this template." That single investigating note is the only update Zapier filed for this incident. No resolved or monitoring update appears in the record, so there is no vendor confirmation of what fixed it or exactly when it cleared, only the 37 minute duration attached to the incident. Zapier did not list any affected components for this incident. No user reports were filed during the window on this page. Zapier's own wording sticks to "some users" and "reports", not a scope figure, so there is no way to say from this record how many accounts saw the hang or the error message. Over the past 90 days Zapier has logged 28 incidents with a median duration of 2 hours 53 minutes, which makes this 37 minute incident shorter than most. Across its history Zapier has logged 577 incidents at a rate of 7.4 a month. Zapier's status page does not say what caused the slowdown or the template loading failures.

Learning

This incident sat in Zapier's template recommendation and setup flow, a layer that lives entirely on Zapier's servers and has nothing to do with the health of your own Zaps or integrations. If you were only watching your own endpoints, or watching whether your Zaps kept firing, you would have had no reason to see this: the template homepage and the "Try it" button are Zapier's own UI and backend, not something your monitoring touches. Over UptimeRobot's own 30 day window, Zapier logged 14 incidents, all 14 resolved, with a median duration of 2h 16m, so a short one-update incident like this one sits well below Zapier's typical pattern. That gap between a brief vendor-logged fault and the longer median duration Zapier normally runs is worth remembering: not every incident on their page runs to the usual length, and not every one gets a full write-up either. Your own monitoring covers your half of the stack, the workflows you built and run. UptimeRobot now watches the provider's half too, so next time something feels off in Zapier's templates or recommendations, you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.