Zoom favicon

Zoom outage on 2026-11-09

zoom.com
November 2026 9 Minor incident

Zoom's inbound SMS service in the AU region broke down for 1 hour 4 minutes starting at 00:07 UTC. The fault sat on Zoom's side of the connection, and Zoom's own status page confirms it.

Started

00:07 UTC

Duration

Lasted 1h 4m

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: SMS (Inbound/Outbound), SMS/MMS (Inbound/Outbound)

What happened?

Zoom logged one incident on 9 November 2026, affecting the components it lists as "SMS (Inbound/Outbound)" and "SMS/MMS (Inbound/Outbound)". The incident title names the AU region specifically and describes a service degradation affecting inbound SMS. At 00:07 UTC Zoom said it was investigating, and was careful to note that outbound SMS remained operational and unaffected throughout. By 00:42 Zoom said it had identified the root cause, though it never published what that cause was. At 00:56 Zoom marked the issue resolved and said it would keep monitoring. The incident closed formally at 01:08 UTC, giving a total duration of 1 hour 4 minutes. That is close to the 58 minute median duration Zoom has posted across its last 66 incidents in a 90 day window, so this one sits in line with its usual pattern rather than standing out as unusual. No user reports were filed during this window. Zoom's status page is the only source on record for this incident, and it carries the full weight of what's known here: four updates, no technical detail beyond "root cause identified", and no public post-mortem.

Learning

This incident only touched inbound SMS delivery inside the AU region, a dependency that sits entirely on Zoom's infrastructure and outside anything you can see from your own application logs. If your product relies on Zoom to receive SMS messages, a check against your own endpoints would have shown nothing wrong, because nothing in your own stack failed. The failure was further upstream, in the carrier or routing layer Zoom uses to hand off inbound AU messages, which is exactly the kind of fault that only shows up when something is watching the provider directly. Zoom's 90 day history shows this happens often enough, 66 incidents with a typical resolution time near an hour, that treating any single one as a one off understates the pattern. UptimeRobot's own 30 day data on Zoom shows 20 incidents, all resolved, with a noticeably longer median duration of 1h 41m than Zoom's self-reported median, a gap worth noting rather than explaining away. 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.