Zoom Learning Webpage was degraded for 1h 43m on 21 October 2026. Zoom pinned the cause on an external vendor, not its own infrastructure.
Started
14:43 UTC
Duration
Lasted 1h 43m
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.
What happened?
Zoom's status page opened an incident at 14:43 UTC titled "Service Degradation Affecting Zoom Learning Webpage". At 14:53 Zoom identified the problem as sitting with an external vendor, saying it was "actively working with our vendor partner to resolve this issue". By 15:08 Zoom said the degradation had been "successfully resolved" but kept the incident in a monitoring state rather than closing it. The incident was not formally marked resolved until 16:25, 1h 43m after it started. That gap between the 15:08 fix claim and the 16:25 close is on the record but unexplained, Zoom does not say what it was watching for in between. No component list was published alongside this incident, so there is no way to see which parts of the Learning Webpage stack were touched. No user reports were filed during this window, so there is no independent account of what the degradation looked like on screen. Four updates were posted in total, covering investigating, identified, monitoring and resolved stages, and all four are shown here. Zoom's own language keeps the fault external throughout, naming a vendor partner rather than its own systems as the source. Over the past 90 days Zoom has logged 69 incidents with a median duration of 48 minutes, so this one ran well longer than Zoom's recent typical.
Learning
This incident sat on a learning webpage, a product surface rather than core meeting infrastructure, and Zoom attributed it to a vendor it depends on rather than its own code. That is a useful pattern to recognise: a page can be unreachable or broken for your end users while every one of your own health checks against Zoom's main API or meeting service stays green, because the fault lived one layer further out, in a vendor Zoom itself relies on. Watching your own endpoints only tells you whether your product can talk to Zoom's core services, it says nothing about a supporting webpage breaking because of a third party behind Zoom. Zoom's history shows this is not rare, 69 incidents in 90 days and over 800 all time, averaging more than ten a month, so degradations of this shape recur often enough to plan for. Over the last 30 days, external monitoring recorded 33 incidents against Zoom with a median duration of 1h 26m, all resolved, which gives you an independent timeline to compare against whatever Zoom's own status page says. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.