Service Degradation Affecting Zoom MyNotes in the US region.
Zoom MyNotes may not work for some users in the US region. Zoom reports that the incident is resolved and that the affected services are restored. Zoom states that the issue occurred between 16:00 UTC and 18:51 UTC on 11/18/2026.
State
Monitoring
Started
Ongoing for
45 min
Worst impact
Notice
Timeline
1 updateMonitoring
45 min 100%
Updates
Times in UTCAs posted by Zoom
On 11/18/2026, Between 16:00 UTC to 18:51 UTC, A subset of users may have experienced issues with Zoom MyNotes in the US region. This incident has been resolved and the affected services have been restored.
Affected components
1Zoom in the last 90 days
Full historyIncidents in 90 days
66
Days with an incident
53
Median duration
1 h 20 min
This incident
44% shorter than the median
Other Zoom incidents
All incidentsZoom·Service Degradation Affecting Subset of Users using Zoom Phone Calls in Europe Region.
Zoom Phone inbound and outbound calls did not work for some users in the EMEA region. Zoom reports that the incident is resolved and the services are restored. The incident lasted 13 minutes.
Zoom·Service degradation affected a subset of users attempting to approve attendees for Webinar Registrations in the North America region.
Zoom Webinar Registration attendee approval did not work for some users in the North America region. The Zoom Web Portal was affected. Zoom reports that the incident is resolved and that it lasted 15 minutes.
Zoom·Service Degradation Affecting Zoom Phone Inbound Calls for Subset of Jio subscribers in India
Zoom Phone inbound calls did not work for some Jio subscribers in India. The affected components were Calling (Inbound/Outbound) and Zoom Phone - APAC - Calling (Inbound/Outbound). Zoom reports that the incident is resolved and lasted 5 hours and 30 minutes.
Zoom·Service Degradation Affecting My Files Functionality in Zoom Hub in US Region
Zoom Hub My Files did not work in the US region. Users got permission errors. Zoom reports that the incident is resolved. It lasted 1 hour and 33 minutes.
Zoom·Service Degradation Affecting Outbound SMS due to an underlying carrier issue in the Australia region.
Zoom outbound SMS did not work in the Australia region. The incident affected SMS/MMS (Inbound/Outbound), SMS (Inbound/Outbound), Zoom Phone - Australia - SMS/MMS (Inbound/Outbound), and Zoom CX - Australia - SMS (Inbound/Outbound). Zoom reports that the incident is resolved. It lasted 82 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