Zoom had two separate incidents on 1 October 2026, one lasting 4h 33m and affecting the Zoom app add-on for Google Calendar, the other lasting 1h 46m and touching Contact Center, Mail, Calendar, Meetings, Recording and more. Both faults sat on Zoom's side, confirmed by Zoom's own status page.
Started
11:52 UTC
Duration
Lasted 4h 33m
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 Meetings, Recording, Zoom Events, Voice Agent, Mail, Voice (Inbound/Outbound), Zoom Virtual Agent, Zoom Contact Center, Calendar, Integrations/Calendar/Plug-In/Add-In
What happened?
The first incident started at 11:52 UTC, when Zoom reported a service degradation affecting users' ability to add the Zoom app in third-party calendar services. By 12:38 UTC Zoom said it had identified the root cause and was working with a partner on a fix. Progress updates followed at 15:07 UTC, still describing work with that partner, until Zoom reported the issue resolved at 16:05 UTC and closed the incident at 16:21 UTC. That one ran for 4h 33m from first report to close. A second incident began at 16:08 UTC, but Zoom's own update places the actual degradation earlier, between 15:33 and 15:37 UTC, affecting incoming and outgoing calls across Contact Center, Virtual Agents, Mail, Calendar, Meetings, Cloud Meeting Recordings, Webinars and Events. Zoom marked that one resolved in the same update that announced it, then filed a formal resolved status at 17:53 UTC, for a total listed duration of 1h 46m. Across the day, ten separate components appear on Zoom's status page as affected. No user reports were filed during either window. Zoom has not published any further explanation of root cause for either incident beyond the partner reference in the first.
Learning
Zoom's own status page is the only record here, and it shows two incidents that trace to problems between Zoom and its infrastructure or partners, not to anything visible from a single endpoint check. The first incident was narrow, a calendar add-on integration, which is the kind of fault that can sit entirely outside a typical uptime check aimed at Zoom's core meeting service. The second affected call routing and several backend components, lasting only a few minutes by Zoom's own account before the broader resolved notice went out an hour and a half later. In both cases, the actual degradation window Zoom describes is shorter and more specific than the time between an incident opening and closing on the status page. Zoom has logged 63 incidents in the past 90 days with a median duration of 51 minutes, so a 4h 33m incident and a 1h 46m incident both ran longer than typical for this vendor. If your own monitoring targets your product's use of Zoom rather than Zoom's internal services, you would have seen nothing to flag, because the fault sat upstream in the parts of the system you cannot see. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
