Is NUACOM down?

We are investigating reports of call history not appearing in the Management Portal and mobile/desktop apps for calls made today. Calls are being processed normally, but today's history is not yet visible in the call log. We are working to restore access to call history and will update you shortly.

We have identified and resolved the cause of the issue that prevented call history from appearing in the Management Portal and apps for calls made this morning. Call history is now being restored. We will continue monitoring and mark this as resolved once all history is fully available.

Resolved. The cause of the missing call history has been corrected, and call history is now fully restored in the Management Portal and apps. Thank you for your patience.

We are receiving reports from customers that their Fanvil phones are displaying the message "TR069 connect server failed". Please don't worry about it: this does not affect the phone system or your service. It only results in a message on the phone's screen. We are investigating and will update you as soon as possible. Thank you for your patience.

Fanvil phones are no longer displaying the "TR069 connect server failed" message. Calls were not affected at any point; the message appeared on the phone's screen only. We are still investigating what caused it and will post a final update once we have confirmed the cause.

This incident is resolved. Fanvil has confirmed that the downtime on their device-management service has ended and all of their services are back up and running. Fanvil phones should no longer show the "TR069 connect server failed" message. Calls were not affected at any point; the message appeared on the phone's screen only. If you still see the message on a handset, please restart the phone and contact our support team if it persists.

We are aware that some customers are experiencing slow performance and occasional errors when using the Management Portal and related services. Our team is investigating and we will post an update as soon as we have more information.

We have identified the cause of the slow performance affecting the Management Portal and related services and a fix has been applied. Performance has been improving since around 12:20 Irish time and we are continuing to monitor. We will post a further update shortly.

This incident has been resolved. Between approximately 11:10 and 11:50 Irish time, some customers experienced slow performance and errors in the Management Portal and related services, and some new calls may have failed to connect or taken longer to set up. Phones that were already registered stayed connected. Service has returned to normal and we will continue to monitor. We apologise for the disruption.

We are aware that some customers using Virgin Media for their internet connectivity are currently experiencing service disruptions, which is impacting their ability to make and receive calls over the Nuacom platform. This is an issue with Virgin Media's network, not with Nuacom's infrastructure. Affected customers should contact Virgin Media directly to resolve their connectivity issues. Our platform and voice services are operating normally. If you are experiencing call issues and are NOT a Virgin Media customer, or if your Virgin Media connection is stable but you are still unable to make/receive calls, please contact our support team.

The brief inbound call disruption reported over the last 30 minutes has been resolved. Calls are now being received normally. We do not yet have confirmation of the root cause, but it may have been related to the earlier Virgin Media connectivity issues affecting some customers. If you continue to experience call delivery problems, please contact our support team. Thank you for your patience.

We're aware that some Yealink desk phones are showing "No Service" or "Invalid Line" and failing to register. Our team has identified the cause and is working through affected accounts to apply the fix. If your Yealink handset is showing this error, please contact our support team — in the cases we've seen so far this has resolved the issue immediately. We'll update this page as remaining accounts are resolved.

A fix has been implemented. We're now monitoring affected accounts to confirm Yealink handsets are registering normally.

A fix has been implemented. We're now monitoring affected accounts to confirm Yealink handsets are registering normally. We'll post a final update once this is confirmed resolved.

This incident is now resolved. The configuration issue that caused some Yealink desk phones to show "No Service" or "Invalid Line" was fixed on the morning of 1 September, and monitoring since then shows affected handsets registering normally with no further reports. A permanent configuration change will follow as part of our normal maintenance and will not affect service. If any handset at your site is still showing this error, please restart it and contact our support team if it does not recover.