Is NUACOM down?

Last checked 3m ago
Current status
NUACOM is up

No incidents right now.

  • Official status page: status.nuacom.com
  • Checked every 5 minutes
  • 11 components tracked

NUACOM is operational right now. Last checked 3m ago; the most recent incident resolved 7d ago.

Real-time NUACOM status, recent outages, and incident history: pulled directly from NUACOM's official status page at status.nuacom.com every 5 minutes. Pingoru tracks 11 NUACOM services and has captured 7 incidents in the last 90 days (99.29% uptime). Get email, Slack, Discord, or webhook alerts the moment NUACOM reports a new incident, free for 3 monitors, no credit card.

Users who monitor NUACOM also follow these Telephony services: Twilio Aircall Dialpad Loom Plivo Nextiva Mitel Telnyx OneSignal Attentive View all 8,000+ providers
NUACOM uptime 99.29% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 4h 20m
    Started Oct 22, 2026, 08:09 AM UTC · Resolved Oct 22, 2026, 12:30 PM UTC
    Cloud PBX
    Timeline · 3 updates
    • investigating · Oct 22, 2026, 08:09 AM UTC

      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.

    • monitoring · Oct 22, 2026, 09:56 AM UTC

      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.

    • resolved · Oct 22, 2026, 12:30 PM UTC

      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.

    Latest: 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 shou…

  2. Resolved 59m
    Started Oct 16, 2026, 10:50 AM UTC · Resolved Oct 16, 2026, 11:50 AM UTC
    Public APIManagement Portal
    Timeline · 3 updates
    • investigating · Oct 16, 2026, 10:50 AM UTC

      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.

    • identified · Oct 16, 2026, 11:39 AM UTC

      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.

    • resolved · Oct 16, 2026, 11:50 AM UTC

      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.

    Latest: 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 servi…

  3. Resolved 22m
    Started Sep 14, 2026, 03:45 PM UTC · Resolved Sep 14, 2026, 04:07 PM UTC
    Timeline · 2 updates
    • 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.

    • 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.

    Latest: 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…

  4. Resolved 1d 7h
    Started Sep 01, 2026, 09:49 AM UTC · Resolved Sep 02, 2026, 05:38 PM UTC
    Cloud PBX
    Timeline · 4 updates
    • 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.

    • 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.

    • 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.

    • 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.

    Latest: 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 moni…

  5. Resolved 4h 3m
    Started Aug 04, 2026, 09:50 AM UTC · Resolved Aug 04, 2026, 01:54 PM UTC
    Incoming CallsOutbound Calls
    Timeline · 7 updates
    • 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.

    • 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.

    • identified · Aug 04, 2026, 10:17 AM UTC

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

    • monitoring · Aug 04, 2026, 10:18 AM UTC

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

    • monitoring · Aug 04, 2026, 10:18 AM UTC

      We are continuing to monitor for any further issues.

    • monitoring · Aug 04, 2026, 10:30 AM UTC

      We are continuing to monitor for any further issues.

    • resolved · Aug 04, 2026, 01:54 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Incident record

Since April 2026 · Statuspage by Atlassian · 11 components checked every 5 minutes
52incidents recorded
16last 12 months
5last 90 days
7 hourstypical duration, 12 months

The longest incident in the last year, Yealink handsets showing "No Service" / failing to register on September 1, 2026, ran for 32 hours. 2 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Incoming Calls7
  • Outbound Calls5
  • Cloud PBX4
  • Desktop App3
  • Mobile App3

Latest incidents

Outage history

Past 90 days · 5 incidents View full outage history →