Zoom favicon

Zoom outage on 2026-11-13

zoom.com
November 2026 13 Minor incident

Zoom Phone calls failed for users with a specific number prefix in Shanghai, China for 7 hours and 15 minutes on 13 November 2026. The fault sat with Zoom's underlying carrier in that region, not with your own calling setup.

Started

09:45 UTC

Duration

Lasted 7h 15m

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: Calling (Inbound/Outbound)

What happened?

Zoom logged one incident on this day, affecting Calling (Inbound/Outbound) only. It started at 09:45 UTC and ran until 16:53 UTC, a span of 7 hours and 15 minutes. The first update said Zoom's team had identified the root cause: a problem affecting Zoom Phone calls for users with a specific phone number prefix in Shanghai, China. That update named Zoom's underlying carrier as the party they were working with on a fix, though it did not describe what had gone wrong on the carrier's side. At 14:21 UTC, roughly four and a half hours in, Zoom reported the issue resolved and said they would keep monitoring. The incident was formally closed at 16:53 UTC with a one-line note that affected services had been restored. No further detail was published beyond those three updates. No user reports were filed during this window, which fits an incident scoped tightly to one city and a narrow set of phone number prefixes rather than Zoom's wider calling base. Zoom's 90-day history shows 67 incidents with a median duration of 1 hour 20 minutes, so this one ran well past what's typical for them. Over the full history Zoom logs incidents at a rate of 10.6 per month.

Learning

This incident sat at the carrier layer, the infrastructure Zoom's phone service depends on to actually route calls once they leave Zoom's own network. A check that pings Zoom's API or logs into the Zoom app would stay green through this, because the parts of Zoom you can reach from outside were working fine. The failure only shows up if you're a caller with the affected prefix trying to complete a call in that one region, which is exactly why no user reports landed during this window. Your own monitoring of your integration with Zoom tells you whether your calls connect, but it can't distinguish "my setup is broken" from "Zoom's carrier in Shanghai is broken" without watching Zoom's side directly. UptimeRobot's own 30-day data on Zoom shows 19 incidents with 18 resolved and a median duration of 2h 12m, a pattern of regional and component-specific faults that rarely surface in broad uptime checks. 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.