Zoom's Calendar service degraded for a subset of users in the US and Europe for 25 minutes on 16 November 2026. Zoom's own status page confirms the fault sat on their side, not in your setup.
Started
17:17 UTC
Duration
Lasted 25m
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: Calendar
What happened?
Zoom logged one incident on this day, starting at 17:17 UTC and resolved by 17:39 UTC, a span of 25 minutes. The affected component was Calendar, and Zoom's own wording describes it as a service degradation affecting a subset of users using the Calendar service in the US and Europe region. Zoom opened with an investigating update at 17:17, said they had identified the root cause nine minutes later at 17:27, moved to monitoring at 17:29 after saying the issue was resolved, and posted a final resolved update at 17:39. Zoom did not publish what the root cause actually was at any point in the four updates, so the cause is not on the record beyond "identified". No user reports were filed during this window, which is consistent with a short fault affecting only part of the user base rather than everyone on the platform. There is no severity label worth repeating here since Zoom's own grading reflects their internal triage, not the actual impact on your calendar syncing or scheduling. For context, Zoom's status page has logged 69 incidents in the past 90 days with a median duration of 1 hour 23 minutes, so this 25 minute incident resolved faster than most. Across all time Zoom has logged 832 incidents, averaging 10.7 per month, which gives a sense of how often some part of the service reports trouble. This particular incident affected one listed component only, with no other services named as impacted in the window.
Learning
When a provider's own status page names a specific component like Calendar rather than the whole platform, it usually means the fault sat in one backend service that only a subset of users touched, in this case calendar sync or scheduling features rather than meetings or chat. If your monitoring only checks whether Zoom's main domain responds, a 25 minute Calendar degradation like this one would not show up as a red flag on your end, because the core service you are pinging stayed up the whole time. This is the general shape of these failures: the headline product works, but a dependent feature underneath it breaks for a slice of users in specific regions, here the US and Europe. Zoom's four updates moved quickly from investigating to identified to monitoring to resolved inside 22 minutes, so by the time most people would notice something odd with calendar invites, it was already fixed. That speed cuts both ways: fast resolution is good news for your users, but it also means a monitoring setup that checks on a longer interval could miss the whole event. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.