Zoom logged two separate incidents on 15 November 2026. The longer one kept the Workflow tab in the Zoom Client broken for 2 hours 52 minutes, and a second, shorter fault hit Zoom Events custom domains with SSL errors for 25 minutes. Both were problems on Zoom's side.
Started
03:36 UTC
Duration
Lasted 2h 52m
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: Zoom Events
What happened?
Zoom's status page recorded two incidents on 15 November 2026, both affecting different parts of the product. The first started at 03:36 UTC as a service degradation affecting users' ability to view the Workflow tab inside the Zoom Client. Zoom said it was investigating at 03:36, identified a root cause by 05:34, moved to monitoring at 05:53 after saying the issue was resolved, and marked it fully resolved at 06:26. That gives a total duration of 2 hours 52 minutes. The second incident began at 09:34 UTC and affected Zoom Events custom domains, with Zoom specifying that the symptom was SSL errors. That one was shorter, resolved by 09:57, for a total of 25 minutes. Zoom's own component list ties the day's disruption to Zoom Events, though the Workflow tab issue sits under the Workflow Service rather than Events itself. No cause is given beyond "root cause identified" for the first incident, and Zoom never states what that cause was. For the second, the only detail offered is the SSL error symptom, with no explanation of why it happened. No user reports were filed in this window, and there is no post-mortem published for either incident on this record.
Learning
Over the last 30 days, UptimeRobot's own checks logged 17 incidents against Zoom, all resolved, with a median duration of 2 hours 25 minutes, which is longer than the median across Zoom's own 90-day history of 1 hour 23 minutes. That gap matters: a feature like the Workflow tab or an SSL certificate on a custom domain can fail while the base Zoom service you ping directly stays reachable, so your own uptime check on your product can stay green through this entire day while the underlying Zoom components were broken. The failure here sits in specific sub-components, a UI tab and a domain's SSL handling, not in the core meeting infrastructure, which is exactly the kind of fault that a simple reachability check on your own endpoints would never surface. Watching only your own service tells you your half is fine, it says nothing about whether the dependency serving a feature inside it has quietly broken. That is why vendor-side monitoring is a separate discipline from monitoring your own stack: your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.