NUACOM had 23 outages in the last 2 years totaling 87h 28m of downtime — averaging 0.9 incidents per month.
There were 23 NUACOM outages since August 6, 2024 totaling 87h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating reports of one-way audio affecting a subset of inbound calls, where the caller cannot be heard by the answering agent.
Small number of accounts may experience issues with incoming audio
The issue has been identified and a fix is currently being applied. We will post a further update once the service has been fully restored.
A fix has been implemented and we are monitoring the results.
Resolved — The outgoing call issue affecting select accounts has been fully resolved. The root cause has been identified and an internal investigation is ongoing to prevent recurrence. We apologise for the disruption caused.
We wanted to let you know that we are currently seeing an issue with outgoing calls affecting a small number of accounts. Our team is on it and working to resolve this as quickly as possible. Incoming calls are working as normal. We will keep you updated and apologise for any disruption caused.
Our team has identified the cause of the outgoing call issue. We are working on a fix right now and aim to have everything back to normal as soon as possible. We will update you again once it is resolved.
A fix has been implemented and we are monitoring the results.
We are pleased to confirm that the outgoing call issue affecting a select number of accounts has been fully resolved.
We are currently experiencing an issue affecting incoming calls. Some customers may find that inbound calls are not being received. Our team is actively investigating the cause. Further updates will be posted here shortly.
We have identified the cause of the issue affecting incoming calls. Our engineers are currently monitoring the situation closely. We appreciate your patience and will continue to provide updates.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating the issue
The issue has been identified and a fix is being implemented.
The issue has now been resolved. To apply the changes, please log out of the mobile app and log back in.
We have identified an issue with a recent update that is affecting our database, slowing it down. We are rolling back the changes and will come with an update soon.
The rollback has been implemented at 10:04 GMT, and we are monitoring the systems.
The issue has been resolved. Apologies for the inconvenience caused.
Investigating / Mitigation To reduce system load, we have temporarily disabled the non-critical Contact Name Look-up, Portal Reports and Call Logs service. We are actively working to resolve the load issue and will restore service as soon as possible.
Our team has identified the issue related to database cluster degradation. During the maintenance throughout the night, the team has restored enough database capacity to cover the core elements of the service. We are continuously monitoring and ready to respond in case of new issues. Apologies to all the clients and partners affected by this incident.
We are investigating this issue
We are currently experiencing degraded system performance, which may result in slower response times. Our engineers have identified the issue and are actively implementing a solution. Thank you for your patience while we work to restore full performance.
Apologies for the delay in providing an update on the system status. Our team is still working toward a full resolution of the issue. The system remains operational; however, you may experience delays when calls are connecting.
Our team has identified the issue related to database cluster degradation. During the maintenance throughout the night, the team has restored enough database capacity to cover the core elements of the service. We are continuously monitoring and ready to respond in case of new issues. Apologies to all the clients and partners affected by this incident.
The incident has been resolved. If you are still experiencing any issues, please don't hesitate to contact our customer care team. Apologies for any inconvenience caused,
We are currently investigating the issue.
The issue with the calls using the desktop app is now resolved, apologies for the inconvenience caused. The team is investigating the root cause.
We are currently investigating this issue.
The incident is now resoved, sorry for the inconvenience caused, the team is continuing the investigation into the root cause.
We are observing issues with the API being slow or unavailable, we are investigating the cause of the issue.
The issue was identified and resolved. The NOC team is monitoring the performance.
The issue is resolved, and the systems are back operational. Apologies for the problems caused.
Wea re currently investigating the this issue
Please reload the desktop app by clicking on View → Reload (located at the top left corner of the app). This will make the app operational again. We apologise for the inconvenience caused.
This incident has been resolved, all systems are fully operational. please reload your desktop app if stilll affected; How to reload the app: 1. Click on “View” in the top-left menu of the app. 2. Select “Reload” from the dropdown.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
One of our SIP gateways (k1) received many requests from the Internet, and it could not process all of them. Some IP handsets have experienced the error "SIP Registration Fail". We found the source of the issue and have resolved the issue. We are increasing the capacity of the system so it can deal with larger volumes of traffic.
One of our SIP gateways (k1) received a large amount of requests from the Internet Due to the high load, it was not able to process all requests. Some IP handsets have experienced the error "SIP Registration Fail". For about 10 min, the IP handsets which have an extension board, would not see the button's indication light working correctly.
We are currently investigating a reported issue affecting the BLF (Busy Lamp Field) functionality on some IP phones. Users may experience delays or failure in BLF status updates, such as incorrect or missing presence indicators (e.g., busy/available/idle). This may affect the call transfer, call pick up in some situations. Our engineering team is actively working to identify the root cause and restore full functionality as soon as possible.
The issue with the BLF (IP handsets expansion panel key lights) has been resolved. The root cause of the issue was the sheer amount of Subscribe requests received from the handsets. We are planning maintenance windows over the weekend to improve the infrastructure configuration and avoid these issues happening again. Sincere apologies to anyone affected.
We are investigating this issue
We are continuing to investigate this issue.
The issue was identified. We were getting flooded with large amounts of traffic. We have implemented a temporary fix by blocking specific types of traffic with the side effect of not having the VoIP handsets extension panels "Busy light indicators" working. This should allow the phones to successfully register and make/receive calls. Further updates will follow. Sincere apologies to the customers affected.
Here's an update on the recent call disruption that affected some clients. A high volume of incoming traffic caused excessive load, leading to intermittent call failures. We have now blocked the specific traffic sources, which has stabilized service. **Some clients will not have their IP phone's side panel button lights working (BFL) until later today when we manage to enable that feature safely.** We will perform a maintenance window tonight to add further safeguards and prevent similar issues from recurring. While we aim to minimize any impact, brief interruptions may occur. We sincerely appreciate your patience and understanding as we work to improve our services. If you have any questions, please feel free to reach out at [email protected].
This incident has been resolved.
We are investigating an incident affecting Management Portal. We will provide updates via email and Statuspage shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Today, from 09:50 to 10:07, we experienced intermittent issues with one of our clusters, which impacted customers connected to it. We took immediate action and are currently working on scaling the affected cluster to multiple nodes to prevent further disruptions. We apologize for any inconvenience this may have caused and appreciate your understanding.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.