All Systems Operational
Poly RealConnect Operational
NALA ? Operational
EMEA ? Operational
APAC ? Operational
Licensing ? Operational
Calling ? Operational
Scheduling ? Operational
RealConnect Tenant Report Operational
One Touch Dial Service Operational
Poly Cloud Operational
Poly Device Management Service for Enterprise (PDMS-E) Operational
Poly Cloud Services Administration Portal Operational
Poly Lens ? Operational
Poly Zero Touch ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
NOTICE:

Poly has announced the End of Sale for PDMS-E as of Dec 15, 2021 to take effect on Feb 15, 2022. To allow our customers adequate time to migrate, we are providing them an extension to the duration of the active PDMS-E service at no cost. Current PDMS-E licenses will not expire until the end of the extension period, which is Oct 1, 2022.

LEARN MORE:

Poly Lens Overview (video)
Account Creation (video)
Invite Team Members (video)
Poly Lens Provisioning and Onboarding Network Devices (video)
Try Poly Lens at NO CHARGE
Check out the Poly Lens Documentation Portal
Speak with your account manager for more information


Interested in participating in the PDMS-E to Poly Lens migration beta? Email betasupport@poly.com

Posted on Dec 17, 2021 - 15:44 MST
As of October 1st, 2022 Microsoft will remove Basic Authentication to Exchange Online. See https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-deprecation-in-exchange-online-september/ba-p/3609437. for additional details. Optionally, you can file a one-time request to extend the timeframe to January 2023 as outlined in the section “Opting Out”. To eliminate any disruption in service Poly recommends to take IMMEDIATE action to review your OTD configuration, in case you do use basic authentication/auto-registration.

If your OTD tenant is already integrated using OAuth and your video devices have calendaring service configured to authenticate using OTD generated credentials, no action is required from you at this time.

However, if your OTD tenant still has video devices with calendaring service configured in auto-registration mode (where O365 credentials are configured directly in the calendar settings of the Poly video device while pointing the server address setting to otd.plcm.vc), Poly recommends you to take IMMEDIATE ACTION and change your authentication type from auto-registration to OTD generated credentials model prior to upcoming October 1st. Detailed instructions on how to create a device, generate new device credentials and configure a Poly device can be found in our online documentation at https://otd.plcm.vc/support/docs/devices/registering-a-device. Failure to update the authorization type to OAuth and re-authorize the calendar integration will result in disruption of auto registration model for Poly endpoints to OTD which utilizes Basic Authorization at the time of deprecation.

It is recommended that any existing OTD configuration using auto registration migrate over to the service account or application identity models before the October 1st deadline set by Microsoft. It is highly recommended to no longer use automatic registration in any new deployments. Any organization setting up the OTD service with Exchange Online for the first time now should use the application identity model outlined in our online documentation at https://otd.plcm.vc/support/docs/calendars/office365-connect-as-application.

If you have any questions, please contact Poly Global Support Services.

Posted on Sep 14, 2022 - 19:28 MDT
Past Incidents
Apr 23, 2024

No incidents reported today.

Apr 22, 2024

No incidents reported.

Apr 21, 2024

No incidents reported.

Apr 20, 2024

No incidents reported.

Apr 19, 2024

No incidents reported.

Apr 18, 2024

No incidents reported.

Apr 17, 2024
Postmortem - Read details
Apr 17, 07:44 MDT
Resolved - This incident has been resolved.
Apr 17, 07:42 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 16, 08:34 MDT
Update - We are continuing to work on a fix for this issue.
Apr 16, 01:24 MDT
Identified - The issue has been identified and a fix is being worked on.
Apr 15, 16:58 MDT
Apr 16, 2024
Apr 15, 2024
Apr 14, 2024

No incidents reported.

Apr 13, 2024

No incidents reported.

Apr 12, 2024

No incidents reported.

Apr 11, 2024
Resolved - This incident has been resolved.
Apr 11, 14:29 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 11, 10:57 MDT
Investigating - We are currently investigating this issue.
Apr 11, 10:30 MDT
Postmortem - Read details
Apr 11, 15:26 MDT
Resolved - This incident has been resolved.
Apr 11, 06:48 MDT
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 10, 13:11 MDT
Update - We are continuing to work on a fix for this issue.
Apr 10, 11:51 MDT
Identified - The issue has been identified and a fix is being implemented.
Apr 10, 10:02 MDT
Update - We are continuing to investigate this issue.
Apr 10, 08:57 MDT
Investigating - We are currently investigating this issue.
Apr 10, 05:37 MDT
Apr 10, 2024
Apr 9, 2024

No incidents reported.