Service Impact to IAD2, LAX1, LAX2, STO1, SYD1, SYD2 Data Center.

The issue has been mitigated, we are continuing to monitor the results.

Netskope is currently developing an Emergency Hotfix (EHF) to address the root cause of this issue and continues to closely monitor the infrastructure. Based on ongoing observations across the affected POPs, the impact is now considered mitigated. We will share further details regarding the EHF deployment in the next update.

Netskope has identified the root cause but is actively investigating various trigger points to prevent a recurrence of the issue. Until a permanent solution is deployed, we will continue to monitor the affected service nodes and promptly perform restarts when the issue is observed. Users whose NPA connections are being handled by these specific nodes may still experience brief disconnections during the restart process. We anticipate providing an update on the final fix within the next 24 hours.

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

Netskope has successfully completed the restart process and is now actively monitoring the status of the affected NPA service nodes.

Netskope has identified that a subset of NPA service nodes are exhibiting high CPU utilization across multiple POPs, which is causing the reported behavior. To mitigate the impact, Netskope is manually restarting these affected nodes. Users whose NPA connections are being handled by these specific nodes may experience brief disconnections during the restart process.

Netskope is actively devising a mitigation strategy and closely monitoring the situation. Our analysis confirms that the impact on other POPs is significantly less severe than the previously affected POPs.

Netskope has identified the root cause and is currently developing the mitigation strategy to resolve the issue.

We are currently investigating this issue.