Netwrix had 7 outages in the last 2 years totaling 1408h 37m of downtime — averaging 0.3 incidents per month.
There were 7 Netwrix outages since September 22, 2025 totaling 1408h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating intermittent performance degradation in the US region.
This incident has been resolved. The team is continuing to investigate the root cause
At 09:55 UTC we encountered an issue with our production environment. The issue was resolved and normal functionality was restored at 10:33 UTC. We are continuing to investigate the incident
This incident has been resolved.
An issue has been identified accessing the 1Secure portal and the team are currently investigating the cause. Background functionality such as activity record importing and alerting are continuing as normal.
We experienced a brief availability issue due to delays in a configuration change being propagated. Propagation is now catching up and service availability should be restored. If you’re still experiencing issues, please try again shortly.
This incident has been resolved.
An issue has been identified performing edit operations within source management.
The cause of the issue has been identified and the team are currently working on a fix.
This issue has now been resolved.
An issue has been identified with the patch 6.2.9 when importing a configuration that has been exported. The import will error out and no changes will be made. Previously exported configurations before the update can still be imported. The team are working on a fix for this issue and a new release will be published as soon as it is available. In the meantime, if you need assistance, please contact the support team.
The issue has been resolved and everything is functioning normally. Thank you for your patience and understanding.
The team are currently investigating an issue relating to uploading File Server activity.
An issue has been identified with agent build v2.0.879.0. The team are working on a fix for this issue and a new agent build will be published as soon as it is available. In the meantime, downgrading to v2.0.873.0 will resolve the issue.
A fix for this issue is now available in agent v2.0.883.