Zoom
Zoom is operational
History
Incidents in 90 days
49
Days with an incident
41
Median duration
47 min
Longest incident
14 days
Components
306Zoom Meetings
Zoom Chat
Oct 19, 2026
This incident has been resolved.status.zoom.us
This incident has been resolved and the affected services have been restored.status.zoom.us
This incident has been resolved and the affected services have been restored.status.zoom.us
Oct 14, 2026
This incident has been resolved and the affected services have been restored.status.zoom.us
This incident has been resolved and the affected services have been restored.status.zoom.us
This incident has been resolved. Please see the following KB article for details on the workaround. https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0089363status.zoom.us
Maintenance
Zoom Phone Maintenance (Sydney Data Center): November 20, 2026
Zoom will perform service maintenance at our SYD1 Data Center starting at 2:00 AM Pacific (or 9:00 PM Sydney) on November 20, 2026. Zoom Phone users registered to those sip zones will be automatically registered in the MEL1 sip zone sequentially. During the maintenance window, a brief disconnection may be experienced and notifications may be missed. If you get disconnected, the system will attempt to reconnect you automatically.
Zoom Phone Maintenance - SA01 - KSA1 Data Center: November 16, 2026
Zoom will perform service maintenance at our SA01-KSA1 Data Center starting at 9:00 AM Pacific on November 16, 2026. Zoom Phone users registered to the those sip zones will be automatically registered in the SA01-RUH1 sip zone sequentially. During the maintenance window, a brief disconnection may be experienced and notifications may be missed. If you get disconnected, the system will attempt to reconnect you automatically.
Zoom Conference Room Connector DNS Changes: November 14, 2026 (No Operational Impact)
We will be undergoing scheduled maintenance during this time.
Zoom Conference Room Connector DNS Changes in Saudi Arabia Region: November 13, 2026 (No Operational Impact)
As part of ongoing service enhancements for the Cloud Room Connector (CRC) service, Zoom will be updating DNS records for SIP/H.323 and IP endpoints in Saudi Arabia region . Effective Date: November 14, 2026 Action Required To avoid service disruption, we recommend reviewing your CRC endpoint configurations as soon as possible, updating your DNS records and Destination ip with the new entries, and removing the older legacy records before November 14, 2026. If you have any questions or issues, please contact Zoom Support. DNS Record Updates Saudi Arabia Region We will update the data-center (DC) domains , along with their respective SRV-Records. An example of the change is as follows: jed.zmvc.us >> sau.zoomcrc.com Records to be replaced (A-Record and SRV-Record): jed.zmvc.us: _h323cs._tcp.jed.zmvc.us _sip._tcp.jed.zmvc.us _sips._tcp.jed.zmvc.us _sip._udp.jed.zmvc.us New records (A-Record and SRV-Record): sau.zoomcrc.com: _h323cs._tcp.sau.zoomcrc.com _sip._tcp.sau.zoomcrc.com _sips._tcp
Zoom Phone Maintenance - EU01 - FRA2 Data Center: November 09, 2026
Zoom will perform service maintenance at our EU01-FRA2 Data Center starting at 9:00 AM Pacific on November 09, 2026. Zoom Phone users registered to the those sip zones will be automatically registered in the AMS2 sip zone sequentially. During the maintenance window, a brief disconnection may be experienced and notifications may be missed. If you get disconnected, the system will attempt to reconnect you automatically.
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.cc/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.cc/feed.xml?providers=zoom/feed subscribe https://outages.cc/feed.xml?providers=zoomGo from tracking outages to fixing production issues with Polylane.
Try Polylane