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.
State
Resolved
Started
Lasted
1 h
Worst impact
Degraded
Timeline
4 updatesInvestigating
38 min 62%
Identified
12 min 20%
Monitoring
11 min 18%
Updates
Times in UTCAs posted by Zoom
This incident has been resolved.
The service degradation affecting Zoom Inbound SMS Service in the AU region has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
We have successfully identified the root cause affecting Zoom Inbound SMS Service in the AU region. Outbound SMS remains operational and unaffected. Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made. Thank you for your patience.
We are currently investigating a service degradation affecting Zoom Inbound SMS Service in the AU region. Outbound SMS remains operational and unaffected. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.
Affected components
4Zoom in the last 90 days
Full historyIncidents in 90 days
53
Days with an incident
46
Median duration
1 h
This incident
About the median
Other Zoom incidents
All incidentsZoom·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 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.
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