Zoom favicon

Zoom outage on 2026-11-12

zoom.com
November 2026 12 Minor incident

Zoom logged two separate incidents on 12 November: a 2h 25m outbound SMS degradation for some US users, and a 37h 49m disruption to Microsoft integrations. Both were attributed to vendors underlying Zoom's own service, not to Zoom's core platform.

Started

02:21 UTC

Duration

Lasted 2h 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: Integrations/Calendar/Plug-In/Add-In, Microsoft OneDrive for Organizations, Zoom Scheduler, SMS/MMS (Inbound/Outbound), SMS (Send meeting invite via SMS)

What happened?

The first incident started at 02:21 UTC, when Zoom identified a service degradation affecting outbound SMS messages for a subset of users in the US region, while inbound SMS kept working. Zoom said it was working with its underlying carrier, and by 04:04 reported the carrier had resolved the issue. It was marked resolved at 04:45, a total of 2h 25m. The second incident began at 19:24 UTC and ran for 37h 49m, far longer than the first. Zoom described it as a service degradation affecting Microsoft integrations due to an underlying vendor issue, naming the root cause as identified from the first update. The components list for the day shows SMS/MMS in both directions, SMS meeting invites, calendar and plug-in integrations, Microsoft OneDrive for Organizations, and Zoom Scheduler, five components in total across the two incidents. Zoom posted again almost four and a half hours later to say it was still working with the vendor, then went quiet until 08:56 the next day, when it reported the issue resolved and continued to monitor, closing the incident at 09:12. No user reports were filed during the window for either incident. No post-mortem has been published explaining why the Microsoft vendor issue took over a day and a half to clear. Zoom's own status updates are the only account on record, and a single vendor filing carries only as much weight as the vendor chooses to give it.

Learning

This is a vendor-dependency failure, not a Zoom platform failure, and that distinction matters for how you read it. The SMS leg broke because Zoom's underlying carrier had a problem, and the Microsoft integrations leg broke because of an issue on Microsoft's side, so Zoom's core meeting service could look fine to your own checks while scheduling, calendar sync, OneDrive integration and SMS invites were all degraded underneath it. If you only monitor whether Zoom's app loads or a meeting starts, you would have seen green through both incidents, because the failure sat in a dependency layer that general uptime checks do not reach. Zoom's own 90 day history shows 67 incidents with a median duration of 1 hour 23 minutes, so a 37h 49m outage is well outside its own typical pattern. The practical shape to recognise: your product can be working while a connected vendor underneath it is not, and the only way to know which side broke is to watch the provider's components directly. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.