Zoom Meetings, Zoom Chat and Zoom Contact Center degraded for 49 minutes starting at 16:01 UTC. Zoom traced the fault to an external vendor, not its own code, and resolved it by 16:48 UTC.
Started
16:01 UTC
Duration
Lasted 49m
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 Meetings, Zoom Contact Center, Zoom Chat
What happened?
Zoom's status page opened an investigation at 16:01 UTC for a service degradation affecting multiple Zoom services. Six minutes later, at 16:07, Zoom identified the cause as an issue with an external vendor, and said it was working with that vendor partner to resolve it. At 16:16 Zoom added that Zoom Phone remained unaffected, narrowing the blast radius to Zoom Meetings, Zoom Chat and Zoom Contact Center. A further update at 16:20 gave no new detail, only that work was ongoing. By 16:24 Zoom reported the degradation resolved and moved to monitoring, and the incident was formally closed at 16:48, 49 minutes after it opened. That duration matches the 49 minute median across Zoom's last 68 incidents over 90 days, which makes this a routine-length event for Zoom even though it touched three components at once. No user reports were filed in this window, so there is no independent account of what you would have seen on screen. Zoom has not published a post-mortem naming the vendor or explaining what failed on their end. All six updates came from Zoom itself, so everything you know about cause traces back to one party describing its own incident.
Learning
When a provider blames an external vendor without naming it, you are left trusting a single account with no independent confirmation, and that is worth remembering the next time Zoom reports a fix. The fault here sat behind Zoom's own infrastructure, in a vendor dependency Zoom relies on for parts of Meetings, Chat and Contact Center, which is not something your own endpoint checks would ever see. If your monitoring of your own Zoom integration stayed green through this window, that is not a contradiction: your checks watch whether your product can reach Zoom, not whether Zoom's vendor stack is healthy behind the scenes. A degradation like this can sit entirely inside Zoom's chain of dependencies and still let your calls through, slower or partially, without tripping anything you control. The shape to recognise is multiple components failing together with a vendor named but not identified, resolved fast, and no further detail offered afterwards. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.