Nexthink incident

Nexthink Service degradation: WebUI access returns 502 errors

Major Resolved View vendor source →

Nexthink experienced a major incident on February 12, 2025, lasting 35m. The incident has been resolved; the full update timeline is below.

Started
Feb 12, 2025, 03:47 PM UTC
Resolved
Feb 12, 2025, 04:23 PM UTC
Duration
35m
Detected by Pingoru
Feb 12, 2025, 03:47 PM UTC

Update timeline

  1. identified Feb 12, 2025, 03:47 PM UTC

    Our teams are investigating a degraded performance impacting the access the WebUI. We are actively working on remediating the issue. We thank you in advance for your patience and understanding while we relentlessly move forward on restoring the service.

  2. monitoring Feb 12, 2025, 03:58 PM UTC

    The issue has been resolved and the access is working as expected with our teams currently monitoring the platform to ensure everything is back to normal. We appreciate and thank you for your patience.

  3. resolved Feb 12, 2025, 04:23 PM UTC

    After monitoring the platform, we can confirm that access is fully restored. The root cause was identified as an issue with the DNS services, which has been corrected. We consider this issue resolved. We apologize for the inconvenience and thank you for your patience.