Previous incidents

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.

We are seeing normal speed consistently over past 5 minutes - we continue to investigate cause

We can see there were several disruptions to Azure Load Balancing service in ZA North at 10:43, 10:52, 10:58, and at 11:01 (all South African local time). This is most likely due to Azure cycling some workloads.

When Azure reset these connections, these result in load spikes which can slow the system down with thousands of users reconnecting at the exact same time. We will raise an issue with Azure to understand why the connections were reset, and we apologise for the inconvenience.

We are seeing service restored - and carrier has confirmed restored