Live

Service Degradation Affecting Microsoft Integrations due to an underlying vendor issue.

0

Zoom Scheduler and Microsoft OneDrive for Organizations, plus Zoom calendar and plug-in integrations, are degraded. Zoom identified the cause as an underlying vendor issue and is working on a resolution.

State

Identified

Started

Ongoing for

23 min

Worst impact

Degraded

Timeline

1 update
19:2419:3019:3619:4219:48
DegradedUpdate postedTimes in UTC

Identified

23 min 100%

Updates

Times in UTC

As posted by Zoom

Identified

We have successfully identified the root cause affecting Microsoft Integrations due to an underlying vendor issue. Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made. Thank you for your patience.

Affected components

6
Zoom SchedulerMicrosoft OneDrive for OrganizationsIntegrations/Calendar/Plug-In/Add-InZoom Website - Integrations/Calendar/Plug-In/Add-InZoom Mail - Zoom SchedulerApps by Zoom - Microsoft OneDrive for Organizations

Zoom in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

56

Days with an incident

47

Median duration

1 h 17 min

This incident

70% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

14 days
median 1 h 17 min
90 days agoToday

Other Zoom incidents

All incidents

Zoom·Service Degradation Affecting Outbound SMS Messages for a subset of users in the US region

Zoom outbound SMS messages did not work for a subset of users in the US region. The incident affected SMS/MMS inbound and outbound services, SMS meeting invites, Zoom Meetings SMS, Zoom Phone North America, and Zoom CX North America. Zoom reports that the incident is resolved and that it lasted about 2 hours and 24 minutes.

Resolved

Zoom·Service Degradation Affecting Zoom Conference Room Connector Services Endpoints in the AMS region.

Zoom Conference Room Connector services do not work for some users in the AMS region. Zoom reports that the incident is resolved. The outage lasted about 2 hours and 35 minutes.

Resolved

Zoom·Service Degradation Affecting a subset of users with ZVA and ZoomMate

On November 9, 2026 , between 23:08 - 23:50 UTC, a subset of users may have experienced issues with ZVA and ZoomMate. This incident has been resolved and the affected services have been restored. Our team will continue to monitor the situation closely and keep you informed of any further developments.

Resolved

Zoom·Service Degradation Affecting Zoom Inbound SMS Service in the AU region

Zoom inbound SMS does not work in the AU region. Zoom Phone and Zoom CX SMS components are affected. Outbound SMS stays operational. Zoom reports that the incident is resolved. It lasted about 60 minutes.

Resolved

Zoom·Service Degradation Affecting Zoom Mail, Calendar and Scheduler.

Zoom Mail, Calendar, and Zoom Scheduler had degraded service. Zoom reported that the incident is resolved. The outage lasted about 97 minutes.

Resolved

Follow Zoom

Your coding agent knows when Zoom is down, and tells you when a failure is theirs, not yours. You can also get Zoom incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "zoom" and tell me if Zoom has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=zoom
Slack
/feed subscribe https://outages.live/feed.xml?providers=zoom

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane