Zapier favicon

Zapier outage on 2026-11-04

zapier.com
November 2026 4 Minor incident

For 3h 31m on 4 November, some visitors to zapier.com couldn't start a chat with Zapier's Sales team. The fault sat with Ada, the third party chat system Zapier uses, not with Zapier's own infrastructure.

Started

20:28 UTC

Duration

Lasted 3h 31m

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 on this day, starting at 20:28 UTC. The title Zapier gave it, "Chat with Sales temporarily unavailable", describes the symptom exactly: some visitors to zapier.com could not open a chat window to reach Sales. Zapier's own update pointed people toward its Support team via a separate help page as a workaround while the issue was open. At 22:42 UTC, Zapier posted that Ada, the chat vendor behind this feature, had identified the problem and implemented a fix from its own end. Zapier said it was seeing functionality return but kept the incident in monitoring status rather than closing it immediately, waiting to confirm the fix held before marking it resolved. The incident closed after 3h 31m total. Zapier did not list any affected components separately for this incident, and no user reports were filed during the window on this record. Only two updates were published for the whole incident, one opening it and one closing the loop with the vendor explanation. That is a thin trail for a three and a half hour incident, but it is what Zapier put on record. There is no post-mortem beyond these two lines, so the underlying cause on Ada's side is not detailed anywhere public. Zapier's own history shows this kind of thing recurring often: 28 incidents in the last 90 days, with a median duration of 2 hours 53 minutes, so this one ran close to typical length for Zapier's recent pattern.

Learning

This incident sat in Zapier's chat widget, a narrow feature that only affects visitors trying to reach Sales through the website, not the automations that run your Zaps. That is a useful distinction if you depend on Zapier for workflow automation: a chat outage on zapier.com tells you nothing about whether your Zaps were still executing normally during those 3h 31m. Zapier's reliance on Ada, a separate chat vendor, also means the actual fix happened outside Zapier's own systems, which is why Zapier's update language deferred to what "they" had done rather than describing its own remediation. If you were only watching your own product's uptime during this window, you would have seen nothing wrong, because the failure sat entirely on Zapier's side, in a component you don't control and can't probe from your end. UptimeRobot's 30 day data for Zapier shows 15 incidents with a median duration of 2h 42m, all resolved, which puts this one in familiar territory rather than an outlier. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time 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.