Is NUACOM down?

Last checked 5m ago
Current status
NUACOM is up

No incidents right now.

Official status page: http://status.nuacom.com · Polled every 5 minutes · 11 components tracked

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

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

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

Recent outages & incidents

Past 90 days
  1. 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…

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

  3. Resolved 17h 14m
    Started Jul 21, 2026, 03:51 PM UTC · Resolved Jul 22, 2026, 09:06 AM UTC
    Incoming Calls
    Timeline · 5 updates
    • 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.

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

    • identified · Jul 21, 2026, 03:52 PM UTC

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

    • identified · Jul 21, 2026, 03:52 PM UTC

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

    • resolved · Jul 22, 2026, 09:06 AM UTC

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

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

  4. Resolved
    Started Jul 21, 2026, 03:50 PM UTC · Resolved Jul 21, 2026, 08:00 AM UTC
    Timeline · 1 update
    • resolved · Jul 21, 2026, 03:50 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.

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

  5. Resolved 2h 32m
    Started Jul 06, 2026, 08:34 AM UTC · Resolved Jul 06, 2026, 11:07 AM UTC
    Incoming Calls
    Timeline · 4 updates
    • investigating · Jul 06, 2026, 08:34 AM UTC

      Small number of accounts may experience issues with incoming audio

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

    • monitoring · Jul 06, 2026, 09:34 AM UTC

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

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

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

Outage history

Past 90 days · 5 incidents View full outage history →