Service Degradation Affecting Zoom Mail, Calendar and Scheduler.
Zoom Mail, Calendar, Zoom Scheduler, and their Zoom Mail subcomponents do not work correctly. Zoom reports that it is investigating the cause and the impact. Zoom started the investigation at 03:32 UTC on 6 November 2026.
State
Investigating
Started
Ongoing for
34 min
Worst impact
Degraded
Timeline
1 updateInvestigating
34 min 100%
Updates
Times in UTCAs posted by Zoom
We are currently investigating a service degradation affecting Zoom Mail, Calendar and Scheduler. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.
Affected components
6Zoom in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
44
Median duration
1 h 2 min
This incident
46% shorter than the median
Other Zoom incidents
All incidentsZoom·Service Degradation Affecting Outbound MMS Services in the US region
Zoom reports that outbound MMS services did not work for some users in the US region. The affected components are SMS/MMS (Inbound/Outbound) and Zoom Phone - NORTH AMERICA - SMS/MMS (Inbound/Outbound). Zoom reports that the incident is resolved, and it lasted about 7 hours and 51 minutes.
Zoom·Service Degradation Affecting the Evaluations Acknowledge Button in Zoom Quality Management in the US Region
This incident has been resolved and the affected services have been restored.
Zoom·Service Degradation Affecting Multiple Zoom Services
This incident has been resolved and the affected service has been restored.
Zoom·Service Degradation Affecting Zoom Meetings Services in the US.
This incident has been resolved.
Zoom·Service Degradation Affecting Zoom Learning Webpage
This incident has been resolved and the affected service has been restored.
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.
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.
https://outages.live/feed.xml?providers=zoom/feed subscribe https://outages.live/feed.xml?providers=zoomFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane