Nexthink incident

Nexthink Service Degradation: WebUI

Minor Resolved View vendor source →

Nexthink experienced a minor incident on February 25, 2025, lasting 19h 32m. The incident has been resolved; the full update timeline is below.

Started
Feb 25, 2025, 04:28 PM UTC
Resolved
Feb 26, 2025, 12:01 PM UTC
Duration
19h 32m
Detected by Pingoru
Feb 25, 2025, 04:28 PM UTC

Update timeline

  1. investigating Feb 25, 2025, 04:28 PM UTC

    We are currently experiencing issues with the Nexthink platform that prevent users from logging in to the WebUI. We are investigating on priority and will provide updates as we have them. Our apologies for the inconvenience.

  2. investigating Feb 25, 2025, 04:59 PM UTC

    We continue to actively work on recovering this infrastructure issue. Thank you for your patience and understanding.

  3. identified Feb 25, 2025, 05:31 PM UTC

    We have identified the infrastructure issue, and we continue to actively work on recovering and stabilizing the service. Thank you for your continued patience and understanding.

  4. identified Feb 25, 2025, 06:00 PM UTC

    We continue to make progress on recovering and stabilizing the service. Thank you again for your continued patience and understanding.

  5. identified Feb 25, 2025, 06:30 PM UTC

    We're making steady progress in recovering and stabilizing the service. We truly appreciate your ongoing patience and understanding.

  6. identified Feb 25, 2025, 07:04 PM UTC

    The issue with accessing the WebUI is stabilized. We are now focusing on remaining service degradation. We sincerely appreciate your continued patience and understanding.

  7. monitoring Feb 26, 2025, 08:35 AM UTC

    The issue with accessing the WebUI has been stabilized, and all services are now up and running. Additionally, collector communication, which was affected during the outage, has been fixed. We are now focusing on monitoring and addressing any remaining service degradation. We sincerely appreciate your continued patience and understanding throughout this process.

  8. resolved Feb 26, 2025, 12:01 PM UTC

    After a thorough monitoring of the platform over an adequate duration, the incident can now be considered resolved. We sincerely apologize for any inconvenience this may have caused and appreciate your patience during this time.