Zoom's ZoomMate feature had a service degradation lasting 28 minutes on 5 October 2026. Zoom's own status page says the cause was identified and fixed within a few minutes of the report, and this was on Zoom's side, not yours.
Started
21:57 UTC
Duration
Lasted 28m
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 logged one incident on this day, affecting ZoomMate services, starting at 21:57 UTC. The status page shows four updates across the 28 minutes the incident was open. At 21:57 Zoom said it was investigating a service degradation with ZoomMate. By 22:02, five minutes later, Zoom said it had identified the root cause, though the update does not say what that cause was. At 22:04 Zoom said the degradation had been resolved and that it would continue monitoring, and the incident was formally closed at 22:21. No component list was published alongside this incident, so there is no breakdown of which specific ZoomMate functions were degraded or for how long each was affected. No user reports were filed during this window, so there is no independent account of what the degradation looked like from outside Zoom. Over the past 90 days Zoom has logged 64 incidents with a median duration of 48 minutes, which makes this 28 minute incident shorter than Zoom's recent typical outage. Over all time Zoom has logged 803 incidents, averaging 10.4 per month, so a single short incident like this one is not unusual for Zoom's track record. The only record of what happened is Zoom's own four status updates, and no post-mortem has been published explaining the root cause beyond the claim that it was identified.
Learning
When a vendor says it identified and resolved a root cause within minutes but never names that cause, you are left with the timeline and nothing else. This incident sat entirely within ZoomMate, a specific feature rather than the whole Zoom product, which is the kind of failure that often never touches your own endpoint checks because your product may not even call that feature during the affected window. That is the general shape of these incidents: a narrow, fast-moving fault inside one vendor component, gone before most monitoring setups would notice a pattern, let alone before a support ticket could be filed. Zoom's history shows 64 incidents in 90 days with a median of 48 minutes, so short, contained incidents like this one are routine for Zoom, not exceptional. Watching your own service tells you whether your product responded correctly during this window, but it cannot tell you whether a Zoom feature was degraded upstream of you. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
