Minor impactResolvedCommunication

Zoom incident: Service Degradation Affecting Customer Using Polycom Devices Going Offline

Zoom reported this minor-impact incident on its official status page on Sep 25, 2026, 17:45 UTC. It was resolved after 14d 10h.

Right now Zoom is operational. Live Zoom status →

🔔 Get alerted when Zoom has issuesFree · email alerts · no credit card
Sep 25, 2026, 17:45 UTC
started
Oct 10, 2026, 04:41 UTC
resolved
14d 10h
duration
Minor
impact

Affected components

  • Devices (Softphones/Deskphones)
  1. resolvedOct 10, 2026, 04:41 UTC

    This incident has been resolved and the affected services have been restored.

  2. monitoringOct 10, 2026, 04:25 UTC

    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.

  3. identifiedOct 10, 2026, 01:32 UTC

    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.

  4. identifiedOct 9, 2026, 01:34 UTC

    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.

  5. identifiedOct 8, 2026, 02:40 UTC

    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.

  6. identifiedOct 7, 2026, 03:02 UTC

    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.

  7. identifiedOct 6, 2026, 01:31 UTC

    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.

  8. identifiedOct 5, 2026, 01:32 UTC

    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.

  9. identifiedOct 4, 2026, 01:28 UTC

    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.

  10. identifiedOct 3, 2026, 01:31 UTC

    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.

  11. identifiedOct 2, 2026, 01:31 UTC

    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.

  12. identifiedOct 1, 2026, 01:33 UTC

    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.

  13. identifiedSep 30, 2026, 01:30 UTC

    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.

  14. identifiedSep 29, 2026, 01:22 UTC

    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.

  15. identifiedSep 28, 2026, 01:19 UTC

    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.

  16. identifiedSep 27, 2026, 10:44 UTC

    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.

  17. identifiedSep 27, 2026, 04:01 UTC

    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.

  18. identifiedSep 26, 2026, 20:01 UTC

    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.

  19. identifiedSep 26, 2026, 13:51 UTC

    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.

  20. identifiedSep 26, 2026, 05:32 UTC

    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.

  21. identifiedSep 26, 2026, 01:31 UTC

    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.

  22. identifiedSep 25, 2026, 22:31 UTC

    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.

  23. identifiedSep 25, 2026, 20:20 UTC

    The root cause affecting service degradation with a subset of users with Polycom devices going offline has been identified. We will keep you informed with timely updates as progress is made.

  24. investigatingSep 25, 2026, 19:11 UTC

    We are continuing to investigate this issue and will provide updates as soon as there is more information to share. Thank you for your patience.

  25. investigatingSep 25, 2026, 17:45 UTC

    We are currently investigating a service degradation with a subset of users with Polycom devices going offline. 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Zoom's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Zoom have incidents?

Zoom reported 34 incidents in the last 90 days. A typical incident lasted 1h 57m. See Zoom's uptime and incident history