Zoom's Conference Room Connector endpoints in the AMS region degraded for 2h 38m on 10 November 2026. Zoom's own status page confirms the fault sat on their side, not yours.
Started
20:25 UTC
Duration
Lasted 2h 38m
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 Conference Room Connector
What happened?
Zoom logged one incident on this day, affecting the Conference Room Connector Services Endpoints in the AMS region. It started at 20:25 UTC and ran until 23:00 UTC, a span of 2h 38m. Zoom's status page describes it as a service degradation affecting a subset of users, not a full outage, and that distinction matters because it tells you the failure was partial rather than total. The first update at 20:25 said Zoom was investigating and working to identify impact and root cause. At 21:16 Zoom said the root cause had been identified, though the public update does not say what that cause was. At 22:36 Zoom reported the degradation resolved and said it would keep monitoring, and the incident was formally closed at 23:00. No cause was ever published publicly. No user reports were filed during this window on this page, so there is no independent account of symptoms from people using the affected endpoints. Only this one component was listed as affected, and only this one incident ran on the day. Zoom's history shows 65 incidents in the last 90 days with a median duration of 1 hour 11 minutes, so this one ran longer than typical for this provider.
Learning
This incident sat specifically in Conference Room Connector infrastructure in one region, a layer that most monitoring aimed at your own application would never touch. If your checks hit Zoom's main meeting APIs or your own backend, they would have stayed green through this entire window, and that green reading would have been accurate for what it tested. Zoom's status page is the only record of the AMS degradation existing at all, which means your visibility into it depended entirely on whether you were watching Zoom's own infrastructure rather than just your integration with it. Over the last 30 days UptimeRobot recorded 18 incidents against this provider with a median duration of 1h 51m, all resolved, which gives you a sense of how often this kind of vendor-side fault occurs even when your own endpoints report nothing wrong. The general shape to recognise is a dependency failing one region or one component at a time, invisible from your side until users in that region start complaining. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.