Zoom Support Maintenance: November 20, 2026
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Zoom.
State
Resolved
Started
Lasted
4 h 3 min
Worst impact
Maintenance
Timeline
6 updatesScheduled
1 min 0%
In progress
4 h 3 min 100%
Updates
Times in UTCAs posted by Zoom
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Maintenance will begin as scheduled in 60 minutes.
We will be performing maintenance on Zoom Support Ticketing and Knowledge Base. Users may experience degraded performance and up to 30 minutes of downtime for Zoom Support’s Knowledge Base and Ticketing during the maintenance window.
We will be performing maintenance on Zoom Support Ticketing and Knowledge Base. Users may experience degraded performance and up to 30 minutes of downtime for Zoom Support’s Knowledge Base and Ticketing during the maintenance window.
Affected components
4Zoom in the last 90 days
Full historyIncidents in 90 days
68
Days with an incident
55
Median duration
1 h 18 min
This incident
Not comparable
Other Zoom incidents
All incidentsZoom·Service Degradation for a subset of users affecting outbound Zoom Phone calls in Australia.
Outbound Zoom Phone calls in Australia did not work for a subset of users. Zoom Phone Calling (Inbound/Outbound) was affected. Zoom reports that the incident is resolved and that the service is restored. The outage lasted 12 minutes.
Zoom·Service degradation affecting multiple services in the US region
Zoom services had intermittent problems in the US region. Affected components include Web Portal, Web Client, Zoom AI, and Zoom Whiteboard. Zoom reports that the incident is resolved and the services are restored. The incident lasted 38 minutes.
Zoom·Service Degradation Affecting Zoom MyNotes in the US region.
Zoom MyNotes had a service degradation in the US region. Zoom reports that the incident is resolved and that the affected services are restored. The incident lasted 86 minutes.
Zoom·Service Degradation Affecting Subset of Users using Zoom Phone Calls in Europe Region.
Zoom Phone inbound and outbound calls did not work for some users in the EMEA region. Zoom reports that the incident is resolved and the services are restored. The incident lasted 13 minutes.
Zoom·Service degradation affected a subset of users attempting to approve attendees for Webinar Registrations in the North America region.
Zoom Webinar Registration attendee approval did not work for some users in the North America region. The Zoom Web Portal was affected. Zoom reports that the incident is resolved and that it lasted 15 minutes.
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