This issue was caused by a request spike to a single media server which began at 09:12, leading to a number of calls to fail.

At 09:27 the cause was identified to be a stuck process, specific to this media server, which has been rectified. Media traffic is being rebalanced to further address this.

We apologise for the brief interruption.

This incident is resolved. We are however still investigating, updates to follow

We are investigating reports of failed calls, updates to follow