Service Degradation Affecting Zoom Events custom domain
Zoom Events custom domain is degraded. Zoom is investigating the problem. Zoom states that it is working to identify the impact and the root cause.
State
Investigating
Started
Ongoing for
15 min
Worst impact
Degraded
Timeline
1 updateInvestigating
15 min 100%
Updates
Times in UTCAs posted by Zoom
We are currently investigating a service degradation affecting Zoom Events custom domain 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
1Zoom in the last 90 days
Full historyIncidents in 90 days
59
Days with an incident
50
Median duration
1 h 21 min
This incident
82% shorter than the median
Other Zoom incidents
All incidentsZoom·Service Degradation Affecting Zoom Workflow Service
Zoom Workflows and Zoom AIC had degraded service on 2026-11-15. Users could not view the Zoom Workflow tab in the Zoom Client. Zoom reports that the incident is resolved. The outage lasted about 2 hours and 50 minutes.
Zoom·Service Degradation Affecting Zoom Phone Calls in China Region
Zoom Phone calls did not work for users with the 86216043 prefix in Shanghai, China. Zoom identified the cause and worked with its carrier. Zoom resolved the incident after about 7 hours and 9 minutes.
Zoom·Service Degradation Affecting Microsoft Integrations due to an underlying vendor issue.
Zoom Scheduler, Microsoft OneDrive for Organizations, and Zoom calendar integrations had degraded service. Zoom reports that the incident is resolved. The outage lasted about 37 hours and 48 minutes.
Zoom·Service Degradation Affecting Outbound SMS Messages for a subset of users in the US region
Zoom outbound SMS messages did not work for a subset of users in the US region. The incident affected SMS/MMS inbound and outbound services, SMS meeting invites, Zoom Meetings SMS, Zoom Phone North America, and Zoom CX North America. Zoom reports that the incident is resolved and that it lasted about 2 hours and 24 minutes.
Zoom·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.
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