Broadvoice Status · History · Incident #127686

RESOLVED

P3 - Cloud NOS: PT worten.cloudcc.nos.pt - Unable to login mobile app

Critical · Started Jan 5, 2026 · 4:43 AM

  • Duration

    22h 3m

  • Severity

    Critical

  • Detection lead

  • User reports

Summary

P3 - Cloud NOS: PT worten.cloudcc.nos.pt - Unable to login mobile app

This incident has been resolved. The intervention that took place to update the NOS Certificates solved the issue in all devices.


  • Started

    Jan 5, 2026 · 4:43 AM

  • Resolved

    Jan 6, 2026 · 2:46 AM

  • Duration

    22h 3m

  • Severity

    Critical

Event timeline

How this incident unfolded

  • Investigating

    Jan 5 · 4:43 AM Broadvoice

    We are currently investigating this issue.

  • Identified

    Jan 5 · 4:56 AM Broadvoice

    Issue is only happening with the mobile APP. There were no interventions scheduled. We have identified via the LOGs that some users can login, so it is not affecting all of the customers. We are able to login with the Support team account login.

  • Identified

    Jan 5 · 5:18 AM Broadvoice

    Support team is able to replicate but DEV team is not able to replicate with the same user. We see successful login from several users. Requesting tests to the customer. DEV team login requests are reaching NGINX. Support team requests are not reaching NGINX. Support team gets the same error when trying with the 5G network. DEV team will try to replicate the domain to see live LOGs in the screen and share the results with the team once this is done.

  • Identified

    Jan 5 · 6:12 AM Broadvoice

    We are still waiting for DEV team to replicate the domain to see the live LOGs in the screen and share the results so that we can continue troubleshooting.

  • Identified

    Jan 5 · 7:16 AM Broadvoice

    DEV team continues to have difficulties to understand the root cause, changing the app to have more details about the error. New tests have started to try to reproduce the error while DEV team is trying to compile another APP version.

  • Identified

    Jan 5 · 8:31 AM Broadvoice

    DEV teams continues to try and determine the root cause of the issue. It could be related to NOS certificates, there is already one intervention scheduled for tonight to update some certificates in order to have fix the certificates missing in the trusted chain. Still it is not clear that the tonight's intervention will solve this current issue.

  • Identified

    Jan 5 · 9:55 AM Broadvoice

    We have just updated Android mobile phone to version 16 and we are now able to login using the Mobile APP in a device that was not able to access previously. We have narrowed the error... now it is only happening with Android devices with version 15 or lower. We are taking this approach as a work around, the tonight's intervention should be able to fix the error in all other devices otherwise we will need to continue the troubleshooting.

  • Identified

    Jan 5 · 11:47 AM Broadvoice

    Waiting for tonight's intervention (NOS Certificates Updates) to see if this is solving the problem for old Android devices with version 15 or lower.

  • Monitoring

    Jan 6 · 1:45 AM Broadvoice

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

  • Resolved

    Jan 6 · 2:46 AM Broadvoice

    This incident has been resolved. The intervention that took place to update the NOS Certificates solved the issue in all devices.

Get alerted before the next Broadvoice outage.

Pulsetic catches degradations minutes before vendors acknowledge them.