For 53 minutes on 12 November, password reset and verified device sign-in emails from Zapier were delayed or not arriving at all. The fault sat with Zapier's mail provider, Mailgun, not with Zapier's own platform.
Started
20:00 UTC
Duration
Lasted 53m
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's status page logged a single incident starting at 20:00 UTC. The update, posted at the same time, says Zapier had received customer reports that password reset emails and Verified Device sign-in emails were delayed or not being received. That one update names the cause directly: "our mail provider is currently working through an issue and has implemented a fix," with a link to Mailgun's own status page. No further update was filed after that, and the incident's total duration is recorded as 53 minutes, so it closed without a separate resolution notice on Zapier's side. No components are listed as affected in the record, and no user reports were logged in this window beyond what Zapier itself describes receiving from its own customers. There is only one update on record for this incident, so everything said here rests on that single filing. Zapier did not publish a post-mortem, and nothing in its status history explains why the fix took the time it did or what exactly Mailgun's issue was. Over the past 90 days Zapier has logged 29 incidents with a median duration of 2 hours 42 minutes, and across its full history it has averaged 7.4 incidents a month. Against that backdrop, 53 minutes is short, and the incident was narrow in scope: emails tied to password resets and device verification, not the core automation platform.
Learning
This incident did not originate inside Zapier's own application. It sat in the email delivery layer, with Mailgun as the named third party, which means checks aimed only at Zapier's dashboard or API would likely have stayed green the whole time. That is not a contradiction: Zapier's core service can be up while a dependency it relies on for a specific function, sending account-security emails, is degraded. The general shape to watch for is a delay or silent failure in a notification path that depends on an external mail provider, something that rarely shows up unless you are specifically monitoring that provider or the emails themselves arriving. Zapier's own 30-day figures show 13 such incidents with a median duration of 2 hours 42 minutes, so this kind of delay is not rare for the service. If you build on Zapier and depend on its email notifications reaching your users promptly, your own monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.