Zoom Team Chat Update
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Zoom.
State
In progress
Started
Ongoing for
42 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
3 min 8%
In progress
39 min 92%
Updates
Times in UTCAs posted by Zoom
Scheduled maintenance is currently in progress. We will provide updates as necessary.
We will be providing an update to Zoom Team Chat. There will be no operational impact. All services will be available during this scheduled update (ZR status might be displayed as offline in the service logs but no operational impact).
Affected components
1Zoom in the last 90 days
Full historyIncidents in 90 days
50
Days with an incident
43
Median duration
1 h 2 min
This incident
Not comparable
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