For 37 minutes on 2 November 2026, Zapier's "Chat with Sales" landing page loaded blank, blocking visitors from reaching the embedded sales chat. The fault sat on Zapier's side, and Zapier's own status page confirms it.
Started
20:31 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's status page logged one incident on 2 November 2026, starting at 20:31 UTC. The page at zapier.com/l/chat-with-sales was loading blank, which meant the embedded sales chat was unreachable for anyone who clicked through to it. Zapier's first update named a workaround: the separate Contact Sales form at zapier.com/l/contact-sales kept working, so visitors could still reach sales through that route. The same update told anyone who hit trouble with both the form and the chat to open a support ticket for manual routing. At 21:01 UTC, thirty minutes later, Zapier posted a second update saying it had started pushing fixes to the page and was monitoring to confirm the fix held. No further update followed, and the incident closed at 37 minutes total. Zapier's status page does not say what caused the page to load blank, only that a fix was pushed and monitored. No components are listed as affected in Zapier's own breakdown, which fits an incident scoped to a single marketing landing page rather than the core Zapier product. No user reports were filed during the window on this page. This was a narrow, single-page fault, not a platform-wide one, and Zapier's two updates are the entirety of the public record.
Learning
This incident sat on a marketing landing page, not on Zapier's automation engine or API, which is the layer most external monitoring is built to watch. A check aimed at zaps running or the API responding would have stayed green the whole time, because that layer never broke. UptimeRobot's own 30 day figures show 13 resolved incidents for Zapier with a median length of 2h 42m, so a short, narrow fault like this one sits well below what's typical. The gap between a quiet uptime check and a real page failure isn't a contradiction, it's two different layers being tested, and this incident broke the one most checks skip. If your product links out to vendor-hosted pages like this one, a blank load on their end won't show up in your own monitoring at all. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.