Service Degradation Affecting Customer Using Polycom Devices Going Offline
This incident has been resolved and the affected services have been restored.
The latest update from Zoom.
State
Resolved
Started
37 d ago
2026-09-25 17:45 UTC
Lasted
14 days
until 2026-10-10 04:41 UTC
Worst impact
Degraded
Timeline
20 updatesIdentified
14 days 100%
Monitoring
16 min 0%
Updates
Times in UTCAs posted by Zoom
This incident has been resolved and the affected services have been restored.
The issue affecting customers using Polycom devices going offline has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the subset of remaining devices that are showing offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
A significant number of Polycom devices are back online, and service has been restored for the majority of affected users. We are continuing to work with our underlying provider to address the remaining service degradation affecting a subset of users whose Polycom devices remain offline. We will continue to monitor the service closely and provide further updates as progress is made. Thank you for your patience and understanding.
We are continuing to work with our underlying provider to address the service degradation affecting a subset of users experiencing Polycom devices going offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
We are continuing to work with our underlying provider to address the service degradation affecting a subset of users experiencing Polycom devices going offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
Our team continue to work with our underlying provider affecting service degradation with a subset of users with Polycom devices going offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
Our team continue to work with our underlying provider affecting service degradation with a subset of users with Polycom devices going offline. We will keep you informed with timely updates as progress is made. Thank you for your patience.
Affected components
2Zoom in the last 90 days
Full historyIncidents in 90 days
49
Days with an incident
41
Median duration
47 min
This incident
440× the median
Other Zoom incidents
All incidentsZoom·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.
Zoom·Service Degradation Affecting Meeting Summaries Via Email.
This incident has been resolved.
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.cc/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.cc/feed.xml?providers=zoom/feed subscribe https://outages.cc/feed.xml?providers=zoomFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane