NUACOM Outage History

NUACOM is up right now

NUACOM had 11 outages in the last 2 years totaling 61h 3m of downtime — averaging 0.5 incidents per month.

There were 11 NUACOM outages since June 5, 2025 totaling 61h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.nuacom.com

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 →

Notice July 23, 2025

Desktop app connection

Detected by Pingoru
Jul 23, 2025, 01:50 PM UTC
Resolved
Jul 23, 2025, 04:39 PM UTC
Duration
2h 49m
Affected: Desktop App
Timeline · 3 updates
  1. investigating Jul 23, 2025, 01:50 PM UTC

    Wea re currently investigating the this issue

  2. investigating Jul 23, 2025, 02:02 PM UTC

    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.

  3. resolved Jul 23, 2025, 04:39 PM UTC

    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.

Read the full incident report →

Minor July 16, 2025

Delay in the connecting of the calls

Detected by Pingoru
Jul 16, 2025, 10:54 AM UTC
Resolved
Jul 16, 2025, 04:59 PM UTC
Duration
6h 4m
Affected: Cloud PBXIncoming CallsOutbound Calls
Timeline · 4 updates
  1. investigating Jul 16, 2025, 10:54 AM UTC

    We are currently investigating this issue.

  2. identified Jul 16, 2025, 11:14 AM UTC

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

  3. monitoring Jul 16, 2025, 11:15 AM UTC

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

  4. resolved Jul 16, 2025, 04:59 PM UTC

    This incident has been resolved.

Read the full incident report →