NUACOM Outage History

NUACOM is up right now

NUACOM had 16 outages in the last 2 years totaling 108h 31m of downtime — averaging 0.7 incidents per month.

There were 16 NUACOM outages since September 16, 2025 totaling 108h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.nuacom.com

Notice September 14, 2026

Virgin Media Internet Connectivity Issues Affecting Customers

Detected by Pingoru
Sep 14, 2026, 03:45 PM UTC
Resolved
Sep 14, 2026, 04:07 PM UTC
Duration
22m
Timeline · 2 updates
  1. investigating Sep 14, 2026, 03:45 PM UTC

    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.

  2. resolved Sep 14, 2026, 04:07 PM UTC

    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.

Read the full incident report →

Minor September 1, 2026

Yealink handsets showing "No Service" / failing to register

Detected by Pingoru
Sep 01, 2026, 09:49 AM UTC
Resolved
Sep 02, 2026, 05:38 PM UTC
Duration
1d 7h
Affected: Cloud PBX
Timeline · 4 updates
  1. identified Sep 01, 2026, 09:49 AM UTC

    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.

  2. monitoring Sep 01, 2026, 10:18 AM UTC

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

  3. monitoring Sep 01, 2026, 10:19 AM UTC

    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.

  4. resolved Sep 02, 2026, 05:38 PM UTC

    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.

Read the full incident report →

Major August 4, 2026

Intermittent call failures affecting some accounts

Detected by Pingoru
Aug 04, 2026, 09:50 AM UTC
Resolved
Aug 04, 2026, 01:54 PM UTC
Duration
4h 3m
Affected: Incoming CallsOutbound Calls
Timeline · 7 updates
  1. investigating Aug 04, 2026, 09:50 AM UTC

    We are investigating reports of intermittent call failures affecting inbound and outbound calls on a subset of customer accounts.

  2. identified Aug 04, 2026, 09:56 AM UTC

    We have identified the cause of the incident as an issue affecting one of our platform databases, which is impacting call handling for a subset of accounts. Our engineering team is actively working on a fix. We will update this incident once the issue is resolved and services are fully restored.

  3. identified Aug 04, 2026, 10:17 AM UTC

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

  4. monitoring Aug 04, 2026, 10:18 AM UTC

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

  5. monitoring Aug 04, 2026, 10:18 AM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Aug 04, 2026, 10:30 AM UTC

    We are continuing to monitor for any further issues.

  7. resolved Aug 04, 2026, 01:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 21, 2026

Intermittent one-way audio on some inbound PSTN calls (upstream carrier)

Detected by Pingoru
Jul 21, 2026, 03:51 PM UTC
Resolved
Jul 22, 2026, 09:06 AM UTC
Duration
17h 14m
Affected: Incoming Calls
Timeline · 5 updates
  1. investigating Jul 21, 2026, 03:51 PM UTC

    We are investigating reports of one-way audio affecting a subset of inbound calls, where the caller cannot be heard by the answering agent.

  2. investigating Jul 21, 2026, 03:51 PM UTC

    Analysis indicates the issue originates with our upstream telephony carrier rather than the Nuacom platform, and it affects individual calls intermittently rather than all traffic. Outbound calls and the majority of inbound calls are unaffected. We have raised a fault with the carrier and will update as we learn more.

  3. identified Jul 21, 2026, 03:52 PM UTC

    The issue has been identified and the issue is raised with upstream provider.

  4. identified Jul 21, 2026, 03:52 PM UTC

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

  5. resolved Jul 22, 2026, 09:06 AM UTC

    This issue was resolved last night 11:30PM by the upstream provider.

Read the full incident report →

Minor July 6, 2026

Issues with incoming audio on calls

Detected by Pingoru
Jul 06, 2026, 08:34 AM UTC
Resolved
Jul 06, 2026, 11:07 AM UTC
Duration
2h 32m
Affected: Incoming Calls
Timeline · 4 updates
  1. investigating Jul 06, 2026, 08:34 AM UTC

    Small number of accounts may experience issues with incoming audio

  2. identified Jul 06, 2026, 08:36 AM UTC

    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.

  3. monitoring Jul 06, 2026, 09:34 AM UTC

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

  4. resolved Jul 06, 2026, 11:07 AM UTC

    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.

Read the full incident report →

Major June 11, 2026

Service Notice — Outgoing Call Issues Affecting Select Accounts

Detected by Pingoru
Jun 11, 2026, 01:50 PM UTC
Resolved
Jun 11, 2026, 02:10 PM UTC
Duration
19m
Affected: Outbound Calls
Timeline · 4 updates
  1. investigating Jun 11, 2026, 01:50 PM UTC

    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.

  2. identified Jun 11, 2026, 02:09 PM UTC

    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.

  3. monitoring Jun 11, 2026, 02:09 PM UTC

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

  4. resolved Jun 11, 2026, 02:10 PM UTC

    We are pleased to confirm that the outgoing call issue affecting a select number of accounts has been fully resolved.

Read the full incident report →

Minor May 6, 2026

Issue with incoming calls

Detected by Pingoru
May 06, 2026, 09:45 AM UTC
Resolved
May 06, 2026, 12:55 PM UTC
Duration
3h 10m
Affected: Incoming Calls
Timeline · 4 updates
  1. investigating May 06, 2026, 09:45 AM UTC

    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.

  2. identified May 06, 2026, 09:53 AM UTC

    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.

  3. monitoring May 06, 2026, 10:03 AM UTC

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

  4. resolved May 06, 2026, 12:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 7, 2026

Mobile app degraded performance, you may have issue to make and receive calls

Detected by Pingoru
Apr 07, 2026, 12:49 PM UTC
Resolved
Apr 07, 2026, 01:22 PM UTC
Duration
32m
Affected: Mobile AppIncoming CallsOutbound Calls
Timeline · 3 updates
  1. investigating Apr 07, 2026, 12:49 PM UTC

    We are investigating the issue

  2. identified Apr 07, 2026, 01:16 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Apr 07, 2026, 01:22 PM UTC

    The issue has now been resolved. To apply the changes, please log out of the mobile app and log back in.

Read the full incident report →

Minor February 19, 2026

Issues making and receiving calls

Detected by Pingoru
Feb 19, 2026, 09:56 AM UTC
Resolved
Feb 19, 2026, 10:31 AM UTC
Duration
34m
Affected: Desktop AppMobile AppCloud PBXIncoming CallsOutbound Calls
Timeline · 3 updates
  1. identified Feb 19, 2026, 09:56 AM UTC

    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.

  2. monitoring Feb 19, 2026, 10:16 AM UTC

    The rollback has been implemented at 10:04 GMT, and we are monitoring the systems.

  3. resolved Feb 19, 2026, 10:31 AM UTC

    The issue has been resolved. Apologies for the inconvenience caused.

Read the full incident report →

Minor January 19, 2026

Contact name look-up, Portal Reports and Call Logs service are temporarily unavailable

Detected by Pingoru
Jan 19, 2026, 11:30 AM UTC
Resolved
Jan 20, 2026, 07:28 AM UTC
Duration
19h 58m
Affected: Public APIDesktop AppMobile App3rd Party Integrations
Timeline · 2 updates
  1. identified Jan 19, 2026, 11:30 AM UTC

    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.

  2. resolved Jan 20, 2026, 07:28 AM UTC

    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.

Read the full incident report →

Minor January 19, 2026

Phone system degraded performance

Detected by Pingoru
Jan 19, 2026, 10:48 AM UTC
Resolved
Jan 20, 2026, 12:39 PM UTC
Duration
1d 1h
Affected: Management PortalCloud PBXIncoming CallsOutbound Calls
Timeline · 5 updates
  1. investigating Jan 19, 2026, 10:48 AM UTC

    We are investigating this issue

  2. identified Jan 19, 2026, 12:20 PM UTC

    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.

  3. identified Jan 19, 2026, 04:38 PM UTC

    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.

  4. monitoring Jan 20, 2026, 07:28 AM UTC

    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.

  5. resolved Jan 20, 2026, 12:39 PM UTC

    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,

Read the full incident report →

Minor December 3, 2025

Issue with call audio using desktop app

Detected by Pingoru
Dec 03, 2025, 11:51 AM UTC
Resolved
Dec 03, 2025, 12:27 PM UTC
Duration
35m
Affected: Desktop App
Timeline · 2 updates
  1. investigating Dec 03, 2025, 11:51 AM UTC

    We are currently investigating the issue.

  2. resolved Dec 03, 2025, 12:27 PM UTC

    The issue with the calls using the desktop app is now resolved, apologies for the inconvenience caused. The team is investigating the root cause.

Read the full incident report →

Minor October 23, 2025

IOS app degraded performance, you may have issue to receive incoming calls

Detected by Pingoru
Oct 23, 2025, 02:36 PM UTC
Resolved
Oct 23, 2025, 03:42 PM UTC
Duration
1h 5m
Affected: Mobile AppIncoming Calls
Timeline · 2 updates
  1. investigating Oct 23, 2025, 02:36 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 23, 2025, 03:42 PM UTC

    The incident is now resoved, sorry for the inconvenience caused, the team is continuing the investigation into the root cause.

Read the full incident report →

Minor September 16, 2025

Degraded performance on the Web applications

Detected by Pingoru
Sep 16, 2025, 08:41 AM UTC
Resolved
Sep 16, 2025, 09:02 AM UTC
Duration
20m
Affected: Public APIManagement PortalDesktop AppMobile AppGoogle Chrome Extension3rd Party Integrations
Timeline · 3 updates
  1. investigating Sep 16, 2025, 08:41 AM UTC

    We are observing issues with the API being slow or unavailable, we are investigating the cause of the issue.

  2. monitoring Sep 16, 2025, 08:53 AM UTC

    The issue was identified and resolved. The NOC team is monitoring the performance.

  3. resolved Sep 16, 2025, 09:02 AM UTC

    The issue is resolved, and the systems are back operational. Apologies for the problems caused.

Read the full incident report →