Resolved -
This incident has been resolved.
May 24, 16:33 MDT
Update -
The fix has now been deployed to all regions and we are monitoring.
May 23, 20:45 MDT
Monitoring -
A fix has been implemented in one of our deployments and we are monitoring the results. In addition, we have observed a dramatic decrease in the instances of the issue across the deployments. We will continue implementing the fix in the rest of the deployments and continue to monitor.
May 23, 11:39 MDT
Update -
A fix is currently being tested in our staging environment.
May 20, 09:55 MDT
Update -
We continue to work on the fix with the highest urgency and will update once an ETA is available.
May 19, 10:01 MDT
Identified -
As a joint discovery with Microsoft, we have identified root cause and are actively working on a fix for testing and release.
May 18, 15:06 MDT
Investigating -
Poly/HP and Microsoft are actively investigating the issue. Redialing the call will in most cases resolve the issue.
May 18, 11:08 MDT