N-Able Incident History

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

1. MonitoringOct 21 · 18:02 UTC

   N-able® has implemented the fix, and this issue is being monitored.

Reported by N-Able on their status page.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

1. MonitoringOct 15 · 14:05 UTC

   A fix has been deployed, and we are continuing to monitor the situation.

Reported by N-Able on their status page.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

1. MonitoringOct 20 · 07:03 UTC

   A fix was applied on the 16th October and Engineering teams are monitoring

Reported by N-Able on their status page.

1. MonitoringOct 14 · 10:30 UTC

   We have identified the cause of delayed vulnerability and patch data processing affecting some partners in the DE region, and a fix has been deployed. Processing has been stable since the fix was applied, and we are monitoring as delayed data catches up. Some partners may continue to see vulnerability, patch and discovery data that is not fully up to date, and scans may take longer than usual to reflect results, until processing has fully caught up. No action is needed from partners. Other regions are not affected.

Reported by N-Able on their status page.

1. MonitoringOct 13 · 12:58 UTC

   N-able® has implemented additional fix and are now seeing mail flow resume across affected environments. We continue to monitor the platform closely to ensure stability and confirm that processing remains healthy. Over the years, some servers configuration has drifted from the standard config: older installations, local customisations, or manual changes. On some of them the resolver no longer reads the folder the new setting was placed in. On those servers the file was present but ignored, so the resolver kept using the old key even though the update appeared to be in place.

Reported by N-Able on their status page.

N-Able published this incident without any update text.

1. UpdateOct 9 · 13:35 UTC

   The majority of the update has now been rolled out and the new version will still be to downloading to some devices as they come online.

Reported by N-Able on their status page.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.

N-Able published this incident without any update text.