Zoom Phone Update - Japan SIP Zones: November 15, 2026 (No Operational Impact)
We will be providing an update to Zoom Phone - Japan SIP zones in Tokyo and Osaka. Please refer to https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0062333 for more details. This update includes virtual streams for custom music on hold management. There is no operational impact. All services will be available during this scheduled update.
The latest update from Zoom.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Zoom
We will be providing an update to Zoom Phone - Japan SIP zones in Tokyo and Osaka. Please refer to https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0062333 for more details. This update includes virtual streams for custom music on hold management. There is no operational impact. All services will be available during this scheduled update.
Affected components
2Zoom in the last 90 days
Full historyIncidents in 90 days
54
Days with an incident
46
Median duration
1 h 9 min
This incident
Not comparable
Other Zoom incidents
All incidentsZoom·Service Degradation Affecting Zoom Conference Room Connector Services Endpoints in the AMS region.
Zoom Conference Room Connector services do not work for some users in the AMS region. Zoom reports that the incident is resolved. The outage lasted about 2 hours and 35 minutes.
Zoom·Service Degradation Affecting a subset of users with ZVA and ZoomMate
On November 9, 2026 , between 23:08 - 23:50 UTC, a subset of users may have experienced issues with ZVA and ZoomMate. This incident has been resolved and the affected services have been restored. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Zoom·Service Degradation Affecting Zoom Inbound SMS Service in the AU region
Zoom inbound SMS does not work in the AU region. Zoom Phone and Zoom CX SMS components are affected. Outbound SMS stays operational. Zoom reports that the incident is resolved. It lasted about 60 minutes.
Zoom·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.
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