If your Zoom-based product sends outbound MMS in the US, you may have seen messages fail or stall for nearly eight hours on 3 November 2026. Zoom traced the fault to its underlying carrier partner in the US region, not to its own platform.
Started
17:18 UTC
Duration
Lasted 7h 54m
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/MMS (Inbound/Outbound)
What happened?
Zoom's status page logged one incident on 3 November 2026, affecting the SMS/MMS component, specifically outbound MMS in the US region. It started at 17:18 UTC and ran for 7h 54m before resolution, with the fix noted at 00:57 UTC and the incident formally closed at 01:10 UTC. Zoom's first update said it was investigating service degradation affecting outbound MMS for a subset of users. Nine minutes later, at 17:27 UTC, Zoom identified the cause as an issue with its underlying carrier in the US region, and said it was working with that carrier partner directly. At 19:55 UTC, more than two and a half hours in, the only update was that Zoom was still working with the carrier, with no new detail on scope or timeline. Nothing further was posted until 00:57 UTC, when Zoom said the degradation had been successfully resolved, followed by a formal resolution thirteen minutes later. No user reports were filed during the window on the record here, and Zoom's own language throughout described the affected group as "a subset of users" without quantifying it further. This was a single incident, not a cluster, so the day is defined by one long, carrier-dependent wait rather than repeated failures.
Learning
This incident sat in the carrier layer, the infrastructure Zoom's messaging relies on to actually hand off MMS to phone networks, not in Zoom's own application code. That distinction matters because a fault at that layer can degrade message delivery for hours while Zoom's core platform, and any uptime check pointed at Zoom's API or web app, stays green the entire time. Checking your own endpoints would only tell you that your product can reach Zoom, not that Zoom can reach the carrier on the other side of the handoff. Over the past 90 days Zoom has logged 64 incidents with a median duration of 51 minutes, so an outage stretching close to eight hours is well outside Zoom's typical recovery pattern. If outbound MMS silently failed or queued for your users that day, the cause was outside anything you control or can fix by changing your own configuration. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.