On 29 October 2026, Zapier's Discord integration broke for some customers using SDK-based flows and Custom Actions. The disruption lasted 2h 42m and the fault sat on Zapier's side.
Started
16:13 UTC
Duration
Lasted 2h 42m
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 16:13 UTC and running for 2h 42m before resolution. The incident, titled "Discord integration issues", affected customers making Discord requests through SDK-based flows and Custom Actions specifically, rather than the Discord integration as a whole. Zapier's own update said as much: "the Discord integration itself is not expected to be affected." That is a narrow scope, and it matters because it tells you this was not a blanket Discord failure but a problem with a specific request path inside Zapier's platform. Zapier also said it "may temporarily disable these requests to mitigate the issue", which points to a mitigation applied on Zapier's infrastructure rather than anything you could have worked around from your end. Only one update was filed for this incident, logged at 16:13 UTC, and no further update marking resolution or explaining the root cause appears in the record. That single filing is what Zapier published, and it carries whatever weight a single status update carries. No user reports were filed during the window shown here. Zapier lists no affected components for this incident on this page, and the record does not name a root cause. Over the past 90 days, Zapier has logged 26 incidents with a median duration of 3 hours 17 minutes, so this one ran shorter than typical. Across all time, Zapier averages 7.4 incidents per month.
Learning
This incident targeted a specific request path, SDK-based flows and Custom Actions hitting Discord, inside Zapier's own platform, which is a layer you cannot see by watching your own endpoints. If your product depends on Zapier triggering Discord actions, your monitoring would show your service as healthy throughout, because the fault never touched your infrastructure. UptimeRobot's own 30 day data for Zapier shows 12 incidents, all resolved, with a median duration of 4h 28m, which is longer than this one and gives you a sense of how long these things typically run. The lesson here is not that your monitoring failed. It is that your monitoring and Zapier's status page are each telling the truth about a different half of the system. Checking your own API endpoints will never catch a failure that lives entirely inside a third party's integration layer. That is the gap this kind of incident exposes every time. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.