Scheduled Zoom Software Quarterly Lifecycle Update: February 06, 2027
Zoom will be enforcing a new minimum version for the following areas, approximately 90 days from now, on February 6, 2027: Zoom Rooms Zoom Node - Agent Zoom Phone Local Survivability (ZPLS) module Meeting SDK (Windows) For more information, such as specific versions we are enforcing, refer to the Zoom Software Quarterly Lifecycle Policy support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061130 To assist with checking the client versions on your account, refer to the Dashboard support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0062208#h_13ce9a73-91e5-4df6-9cb5-c815b1605cf5
The latest update from Zoom.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Zoom
Zoom will be enforcing a new minimum version for the following areas, approximately 90 days from now, on February 6, 2027: Zoom Rooms Zoom Node - Agent Zoom Phone Local Survivability (ZPLS) module Meeting SDK (Windows) For more information, such as specific versions we are enforcing, refer to the Zoom Software Quarterly Lifecycle Policy support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061130 To assist with checking the client versions on your account, refer to the Dashboard support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0062208#h_13ce9a73-91e5-4df6-9cb5-c815b1605cf5
Affected components
2Zoom in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
44
Median duration
1 h 17 min
This incident
Not comparable
Other Zoom incidents
All incidentsZoom·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.
Zoom·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.
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