A single feature inside Zoom Quality Management broke for 16h 35m on 28 October. The evaluations acknowledge button went missing from reports in the US region, and the fault sat entirely on Zoom's side.
Started
14:31 UTC
Duration
Lasted 16h 35m
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 Quality Management
What happened?
Zoom logged one incident on this date, starting at 14:31 UTC and running until resolution at 07:06 UTC the next day, a span of 16h 35m. The only component named is Zoom Quality Management, and the only symptom described is a missing evaluations acknowledge button in reports for the US region. That is a narrow, specific failure: it affected a button inside a reporting workflow, not calls, meetings or video itself. Zoom's status page says it identified the root cause at the 14:31 update, then posted two holding updates at 20:33 and 02:58, both saying only that work continued. At 03:19 Zoom moved the incident to monitoring, stating the degradation was resolved, and then closed it fully at 07:06 with a one-line resolved note. Across five updates over more than 16 hours, Zoom never explained what the root cause actually was. You are told it was found, but not what it was. No user reports were filed during the window on this page, so there is no first-hand account of how the missing button affected anyone's workflow. Zoom's own 90-day history shows 68 incidents with a median duration of 49 minutes, which puts this one well outside the typical length. Across all time Zoom has logged 823 incidents, averaging 10.6 a month, so a single-component issue like this is not unusual in frequency, just in how long it ran.
Learning
This incident sat inside a specific feature of Zoom's Quality Management product, a reporting workflow layer rather than core meeting infrastructure, which is exactly the kind of fault that an uptime check against your own endpoints would never catch. Your monitoring tells you whether your product can reach Zoom's APIs and whether calls connect. It does not tell you whether a button inside Zoom's own reporting UI has disappeared, because that fault lives entirely inside Zoom's application layer, not in any path your infrastructure touches. Zoom's status page is the only record of this one, and a single vendor filing carries only as much weight as that vendor chooses to give it: five updates, no explanation of the root cause, no breakdown of how many accounts or reports were affected. The gap between a working connection to Zoom and a broken feature inside Zoom is precisely where incidents like this live, and it is a gap your own checks cannot see across. When something inside a vendor's product breaks while your integration with that vendor still works fine, both readings are correct at the same time. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.