Poly had 47 outages in the last 2 years totaling 1763h 20m of downtime — averaging 1.9 incidents per month.
There were 47 Poly outages since September 6, 2024 totaling 1763h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating the issue.
a fix is in place, continuing to monitor.
issue has been resolved
EU-based Lens system components are experiencing instability. Site access for EU-based users and devices may be affected. Currently US-based resources are operating effectively. Development team is investigating!
Restoration in progress.
This incident has been resolved.
We are currently investigating this issue.
A fix is place and we are monitoring the results.
issue has been resolved
issue has been resolved
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Microsoft has updated the timeline for the identified the issue in the backend EXO and the expected ‘rollout’ of the fix to full ‘WW’ production endpoints will now be Tuesday, March 17th, 2026.
The WW fix applied by Microsoft has not resolved the issue and they are continuing to investigate the underlying cause of the throttling behavior in the Calendaring integration. Further updates will be posted as more information is available. The next expected update is March 19th. Until the issue is resolved, degraded performance will be seen in the Lens Calendaring integration.
A subset of infrastructure that processes Microsoft Graph API queries through a custom app isn't processing requests as efficiently as expected, which is resulting in impact. The Microsoft team deployed a fix has not resolved the issue. They continue to investigate the underlying cause of the throttling behavior. We’ll provide further updates as soon as more information is available.
Microsoft has completed the WW rollout of their fix and system functionality has returned to normal.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating issues where newly created user sessions (sign-in) are failing to connect to IoT. Loginless onboarding and existing applications which have valid refresh tokens remain connected to IoT as expected.
A fix has been implemented and we are monitoring the results.
A recent update to one of our APIs introduced an issue that prevented certain registrations from completing. The update has been rolled back, and the issue is now resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Starting at approximately 16:00 UTC, our provider (Microsoft) began experiencing DNS issues resulting in availability degradation of some services. unfortunately this also appears to impacting our DNS records for Poly Lens. See https://azure.status.microsoft/en-us/status for additional information.
The issue appears to be related to a current Microsoft Azure CDN outage.
The provider has successfully reverted their service changes in the affected regions. The web portal is now accessible, and we are actively monitoring the service for any further issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This issue has been resolved. The cause was twofold: 1) a security update on some of our hosts that led to increased memory consumption during peak hours, and 2) an update from our IoT provider that caused a higher connection load on a specific instance. We have since scaled our instances and added additional memory consumption metrics to monitor performance going forward.
An update to VM image which included additional cyber monitoring increased our memory consumption at peak times; this combined with an update from our IoT provider that caused a higher connection load on a specific instance created a compound problem that created the slow API responses for device details. We scaled our instances and added additional memory consumption metrics to monitor performance going forward.
A subset of the devices connected are reporting "Remote Access is unavailable because the device state is unknown"
A fix has been implemented and we are monitoring the results.
The incident has been resolved. An underlying scalability issue in one of our IoT Hubs was identified as the root cause, which impeded the timely delivery of cloud-to-device messages and consequently resulted in remote access failures for certain devices.
We are currently investigating this issue.
We are continuing to investigate issues within our message pipelines that are impacting service delivery, particularly affecting response times for Remote Access and the Admin UI page.
We’ve resolved the issue affecting page load times in the Admin UI. Our team is continuing to investigate the ongoing issues related to Remote Access and will provide further updates as we learn more. Thank you for your patience.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
On the Device Inventory page, clicking on the lines ("phone") icon, the page will only display a spinning "Loading..." status. The Phone's line information is not shown. We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue whereby OTD administrator may experiencing authentication failures when signing in to OTD portal. Calendar registration is not affected.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This was a false positive repose in our monitoring system.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
Device-related data and state information is noticeably delayed in updating current status.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.