Zoom Mail, Calendar and Scheduler went down for 1h 39m on 6 November 2026. Zoom's own status page confirms the fault sat on its side, in the backend serving these three components.
Started
03:32 UTC
Duration
Lasted 1h 39m
Source
IsDown
Next time
Zoom 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.
Affected components: Mail, Zoom Scheduler, Calendar
What happened?
Zoom logged one incident on this day, starting at 03:32 UTC and resolved by 05:09 UTC, a total of 1h 39m. The incident title names three affected components: Zoom Mail, Calendar and Scheduler, and Zoom's updates treat all three as a single degradation rather than separate faults. At 03:32 Zoom opened the incident as "investigating", saying it was working to identify impact and root cause. By 04:06, 34 minutes later, Zoom moved to "identified", stating the root cause had been found, though the public updates never say what that cause was. At 04:34 Zoom marked the issue as resolved under a "monitoring" status, and the final "resolved" update followed at 05:09. That is four updates across the full 1h 39m window, which is the complete record Zoom published for this incident. No user reports were filed during the window, so there is no independent account of what the degradation looked like from inside Mail, Calendar or Scheduler. Zoom's status page is the only source here, and it carries the full weight of this page's account since nothing else corroborates or contradicts it. Over the past 90 days Zoom has logged 65 incidents with a median duration of 52 minutes, so this one ran longer than typical. Across all time Zoom averages 10.6 incidents a month, out of 824 recorded total.
Learning
This incident sat in Zoom's backend services for Mail, Calendar and Scheduler, not in the layer a simple uptime ping against your own product would touch. If your product only checks that your own endpoints respond, a Zoom backend degradation like this one can run its full course without tripping any alert you own, because your servers were up the whole time even while the data they depend on from Zoom was degraded. UptimeRobot's own 30 day figures for Zoom show 22 incidents, all resolved, with a median duration of 1h 41m, close to the length of this one, meaning this kind of outage is routine rather than exceptional for this provider. The pattern worth recognising is the gap between "my service is reachable" and "the provider behind my service is working correctly", and that gap is exactly where this incident lived. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.