Get updates
Preferences
Web Application - Operational
Previous page
Next page
Myphoner Voice - Operational
Marketing and Documentation Pages - Operational
Marketing and Documentation Pages
Support Widget/Chat - Operational
Support Widget/Chat
Support Backend - Operational
Support Backend
No notices reported this month
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.
One of our main routes for telephony has been experiencing an Internet attack (DDOS) similar to the incident from 17 November (4 days ago). We are working on rerouting traffic to other providers in order to normalize the service. We will keep updating this incident as we get updated ourselves.
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 experiencing an issue where the dialer for Myphoner Voice is not initializing correctly, causing the dialer to connect & disconnect continuously. We are investigating the issue in order to resolve it and will provide an update shortly.
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.
One of our main routes for telephony has been experiencing an Internet attack (DDOS) for a little more than an hour, and we are working hard to reroute traffic and stabilize the situation. Unfortunately, this has affected all customers using voice and are still affecting some. We will keep updating this incident as we get updated ourselves.
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.
We are currently experiencing slow response times which is causing time outs to occur, this is greatly affecting the lead view portion of the platform. The issue has been identified and we are realising a fix to resolve it within the next 30 minutes.
A release with an associated database migration got out of sync and caused pages to respond with error 500. All customers were affected for about an hour. Once we got the database migrated correctly the error was resolved. The main reason for this incident was human error - the procedures for database migrations was not followed properly. As a consequence, we are taking steps to ensure that procedures are followed accordingly going forward.
Previous
Nov 2021 to Jan 2022
Next