Current routes are stable and we are closing this incident now, however, we continue to monitor the situation and work with our downstream providers to ensure access to secure and stable routes going forward.

We are monitoring the situation with regards to calls to the US and aim to provide an update as soon as we have further information from our voice engineers and providers.

Calls to affected the affected region (the US) has stabilized and are working well through the current routes. We will continue to monitor and update where appropriate.

We have successfully made routing changes and are monitoring calls going through to the providers. We are monitoring to ensure the stability of the calls and will update you as the situation changes.

Engineers have been investigating the issue and can confirm that: As load rose on the servers handling voice client connections, the normal load-balancing procedures did not take over as expected, and the servers started to run out of memory. Engineers were able to spot the issue within minutes and restore service to normal. We have since found a weak point in the load balancing and the procedures around the maintenance of the same, steps have been taken to avoid a situation like this in the future. We apologize for the inconvenience caused.

We have investigated the issue and believe that the issue was due to a memory issue on a server, restarting the server has resolved the issue. We are monitoring the dialler closely to ensure that there is no further degraded performance.

We are continuing to route around the affected main route and monitor the situation, but we are closing this incident now as all activity is back to normal and has been so for a long time.

We are continuing to route around the affected main route and monitor the situation. Next update in a few hours latest.

We are continuing to monitor for further issues. Downstream providers are maintaining a degraded status, and so are we. Currently, services have returned to normal and all customers should be able to conduct calls as usual. We will update again in one hour unless there are significant changes in the situation.

We are actively rerouting traffic and monitoring the situation. Most customers should experience service as normal again.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are still seeing issues with performance. We have identified the cause and are working to correct it.

There was a connection failure to our redris that coincided with the deploy to fix the issue. This may have resulted in some users seeing error 500's. We are actively monitoring the platform to mitigate any subsequent issues.

We are continuing to work on a fix for this issue.

Our web host engineers have identified the cause of the issues and mitigated the impact, they are continuing to monitor as are we. Myphoner has been stable for over one hour.

Our web host engineers have identified the cause of the issues and mitigated the impact, they are continuing to monitor as are we. Myphoner has been stable for over one hour.

Our web host is still reporting issues, but Myphoner is back up. We are continuing to monitor the situation closely.

An update from our web host: "Engineers have identified the issue for Common Runtime apps in the EU Region and actively working on resolving the issue. The requests to these applications would fail with a timeout."

Web host engineers are still struggling to get systems operational. Myphoner is not yet stable, unfortunately.

The app seems to be coming back on its legs now. We are still monitoring as our web host is bringing their services back online.