Microsoft Phone System Queues Failing

%3CLINGO-SUB%20id%3D%22lingo-sub-330633%22%20slang%3D%22en-US%22%3EMicrosoft%20Phone%20System%20Queues%20Failing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-330633%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20been%20experiencing%20issues%20here%20in%20Australia%20for%20the%20past%201hour%2B%20that%20is%20affecting%20all%20of%20our%20Microsoft%20Phone%20System%20customers.%20Calls%20that%20are%20routing%20to%20Queues%20are%20simplying%20%22ringing%20out%22%20and%20it%20never%20rings%20the%20Teams%2FSkype%20Clients%20(queue%20members).%20We%20have%20raised%20a%20Service%20Request%20with%20MS%2C%20but%20are%20yet%20to%20receive%20a%20response.%20It%20is%20affecting%20CCE%2C%20Skype%20Online%20and%20Teams%20Direct%20Routing%20customers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20others%20experiencing%20issues%3F%20Do%20you%20have%20any%20update%20from%20MS%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-330633%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-332615%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Phone%20System%20Queues%20Failing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332615%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20anyone%20interested%20this%20was%20indeed%20a%20Microsoft%20Platform%20fault.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22%3CEM%3EPrimary%20root%20cause%20for%20this%20service%20interruption%20was%20%E2%80%98An%20update%20to%20the%20infrastructure%20facilitating%20the%20Skype%20for%20Business%20network%20had%20become%20degraded.%20%E2%80%99%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CEM%3EWe've%20completed%20restarting%20the%20affected%20infrastructure%20and%20confirmed%20mitigation%20with%20some%20of%20the%20affected%20users%20and%20via%20monitoring.%20Scope%20of%20impact%3A%20This%20issue%20could%20have%20potentially%20affected%20any%20of%20your%20users%20intermittently%20if%20they%20were%20routed%20through%20the%20affected%20infrastructure.%20Start%20time%3A%20Tuesday%2C%20February%205%2C%202019%2C%20at%201%3A30%20AM%20UTC%20End%20time%3A%20Tuesday%2C%20February%205%2C%202019%2C%20at%206%3A10%20AM%20UTC%20Preliminary%20root%20cause%3A%20An%20update%20to%20the%20infrastructure%20facilitating%20the%20Skype%20for%20Business%20network%20had%20become%20degraded.%20Next%20steps%3A%20-%20We%E2%80%99re%20reviewing%20our%20code%20for%20improved%20performance%20and%20potential%20automated%20recovery%20options%20to%20reduce%20or%20avoid%20similar%20impact%20in%20the%20future.%20This%20is%20the%20final%20update%20for%20the%20event%3C%2FEM%3E.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

We've been experiencing issues here in Australia for the past 1hour+ that is affecting all of our Microsoft Phone System customers. Calls that are routing to Queues are simplying "ringing out" and it never rings the Teams/Skype Clients (queue members). We have raised a Service Request with MS, but are yet to receive a response. It is affecting CCE, Skype Online and Teams Direct Routing customers.

 

Are others experiencing issues? Do you have any update from MS?

1 Reply
Highlighted

For anyone interested this was indeed a Microsoft Platform fault.

 

"Primary root cause for this service interruption was ‘An update to the infrastructure facilitating the Skype for Business network had become degraded.​’

 

We've completed restarting the affected infrastructure and confirmed mitigation with some of the affected users and via monitoring. Scope of impact: This issue could have potentially affected any of your users intermittently if they were routed through the affected infrastructure. Start time: Tuesday, February 5, 2019, at 1:30 AM UTC End time: Tuesday, February 5, 2019, at 6:10 AM UTC Preliminary root cause: An update to the infrastructure facilitating the Skype for Business network had become degraded. Next steps: - We’re reviewing our code for improved performance and potential automated recovery options to reduce or avoid similar impact in the future. This is the final update for the event."