Netwrix Outage History

Started Oct 23, 2026, 07:43 AM UTC· resolved Oct 23, 2026, 05:47 PM UTC

1. investigating Oct 23, 2026, 07:43 AM UTC

   We are currently experiencing intermittent functionality issues with NIM. Our engineering team is actively investigating the matter to identify the root cause and implement a resolution. Further updates will be provided as more information becomes available.

2. monitoring Oct 23, 2026, 07:57 AM UTC

   Services have been restored. We are currently investigating the cause for the outage. Further updates will be provided as more information becomes available.

3. resolved Oct 23, 2026, 05:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 11, 2026, 02:41 PM UTC· resolved Sep 18, 2026, 02:23 PM UTC

1. investigating Sep 11, 2026, 02:41 PM UTC

   We are currently experiencing intermittent functionality issues with NIM. Our engineering team is actively investigating the matter to identify the root cause and implement a resolution. Further updates will be provided as more information becomes available.

2. investigating Sep 11, 2026, 05:23 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 11, 2026, 05:52 PM UTC

   We are currently monitoring the environment closely.

4. resolved Sep 18, 2026, 02:23 PM UTC

   This incident has been resolved. Our team's investigation determined that the disruption was caused by an issue within Microsoft Azure's infrastructure, unrelated to NIM. We are continuing to investigate with Azure to fully understand the root cause.

Read the full incident report →

Started May 22, 2026, 12:19 PM UTC· resolved May 22, 2026, 12:49 PM UTC

1. investigating May 22, 2026, 12:19 PM UTC

   We are currently investigating intermittent performance degradation in the US region.

2. resolved May 22, 2026, 12:49 PM UTC

   This incident has been resolved. The team is continuing to investigate the root cause

Read the full incident report →

Started Feb 04, 2026, 10:30 AM UTC· resolved Feb 04, 2026, 08:09 PM UTC

1. investigating Feb 04, 2026, 10:30 AM UTC

   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

2. resolved Feb 04, 2026, 08:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 08, 2026, 01:54 PM UTC· resolved Jan 08, 2026, 03:21 PM UTC

1. identified Jan 08, 2026, 01:54 PM UTC

   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.

2. monitoring Jan 08, 2026, 02:03 PM UTC

   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.

3. resolved Jan 08, 2026, 03:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2025, 07:06 PM UTC· resolved Nov 06, 2025, 10:37 AM UTC

1. investigating Nov 04, 2025, 07:06 PM UTC

   An issue has been identified performing edit operations within source management.

2. identified Nov 05, 2025, 09:57 AM UTC

   The cause of the issue has been identified and the team are currently working on a fix.

3. resolved Nov 06, 2025, 10:37 AM UTC

   This issue has now been resolved.

Read the full incident report →

Started Oct 29, 2025, 04:27 PM UTC· resolved Oct 29, 2025, 11:59 PM UTC

1. identified Oct 29, 2025, 04:27 PM UTC

   We are currently investigating an issue affecting connectivity and performance due to an ongoing outage with Microsoft Azure and Azure Front Door. This may result in degraded performance or intermittent errors for customers accessing our services. We are monitoring Microsoft’s status updates and will provide additional information as it becomes available.

2. monitoring Oct 29, 2025, 04:33 PM UTC

   Microsoft has confirmed a widespread outage impacting Azure and Azure Front Door. This may cause latency or service interruptions for users accessing our platform. We are continuing to monitor the situation and will update once mitigation steps are in place. https://azure.status.microsoft/en-gb/status

3. monitoring Oct 29, 2025, 09:58 PM UTC

   Currently access to Netwrix 1Secure maybe intermittent. Update from Microsoft Current status: We initiated the deployment of our ‘last known good’ configuration, which has now successfully completed. We are currently recovering nodes and re-routing traffic through healthy nodes. As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored. This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover. We expect continued improvement across affected regions. This means we expect recovery to happen by 23:20 UTC on 29 October 2025

4. resolved Oct 29, 2025, 11:59 PM UTC

   Microsoft has identified and resolved the issues affecting Azure and Front Door services. Access to our systems should now be fully restored. We are continuing to monitor to ensure stability.

5. postmortem Oct 30, 2025, 09:18 AM UTC

   **What happened?** Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, customers and Microsoft services leveraging Azure Front Door \(AFD\) may have experienced latencies, timeouts, and errors. Affected Azure services include, but are not limited to: App Service, Azure Active Directory B2C, Azure Communication Services, Azure Databricks, Azure Healthcare APIs, Azure Maps, Azure Portal, Azure SQL Database, Azure Virtual Desktop, Container Registry, Media Services, Microsoft Copilot for Security, Microsoft Defender External Attack Surface Management, Microsoft Entra ID \(Mobility Management Policy Service, Identity & Access Management, and User Management UX\), Microsoft Purview, Microsoft Sentinel \(Threat Intelligence\), and Video Indexer. Customer configuration changes to AFD remain temporarily blocked. We will notify customers once this block has been lifted. While error rates and latency are back to pre-incident levels, a small number of customers may still be seeing issues and we are still working to mitigate this long tail. Updates will be provided directly via Azure Service Health. **What went wrong and why?** An inadvertent tenant configuration change within Azure Front Door \(AFD\) triggered a widespread service disruption affecting both Microsoft services and customer applications dependent on AFD for global content delivery. The change introduced an invalid or inconsistent configuration state that caused a significant number of AFD nodes to fail to load properly, leading to increased latencies, timeouts, and connection errors for downstream services. As unhealthy nodes dropped out of the global pool, traffic distribution across healthy nodes became imbalanced, amplifying the impact and causing intermittent availability even for regions that were partially healthy. We immediately blocked all further configuration changes to prevent additional propagation of the faulty state and began deploying a ‘last known good’ configuration across the global fleet. Recovery required reloading configurations across a large number of nodes and rebalancing traffic gradually to avoid overload conditions as nodes returned to service. This deliberate, phased recovery was necessary to stabilize the system while restoring scale and ensuring no recurrence of the issue. The trigger was traced to a faulty tenant configuration deployment process. Our protection mechanisms, to validate and block any erroneous deployments, failed due to a software defect which allowed the deployment to bypass safety validations. Safeguards have since been reviewed and additional validation and rollback controls have been immediately implemented to prevent similar issues in the future. **How did we respond?** * 15:45 UTC on 29 October 2025 – Customer impact began. * 16:04 UTC on 29 October 2025 – Investigation commenced following monitoring alerts being triggered. * 16:15 UTC on 29 October 2025 – We began the investigation and started to examine configuration changes within AFD. * 16:18 UTC on 29 October 2025 – Initial communication posted to our public status page. * 16:20 UTC on 29 October 2025 – Targeted communications to impacted customers sent to Azure Service Health. * 17:26 UTC on 29 October 2025 – Azure portal failed away from Azure Front Door. * 17:30 UTC on 29 October 2025 – We blocked all new customer configuration changes to prevent further impact. * 17:40 UTC on 29 October 2025 – We initiated the deployment of our ‘last known good’ configuration. * 18:30 UTC on 29 October 2025 – We started to push the fixed configuration globally. * 18:45 UTC on 29 October 2025 – Manual recovery of nodes commenced while gradual routing of traffic to healthy nodes began after the fixed configuration was pushed globally. * 23:15 UTC on 29 October 2025 - PowerApps mitigation of dependency, and customers confirm mitigation. * 00:05 UTC on 30 October 2025 – AFD impact confirmed mitigated for customers. **What happens next?** Our team will be completing an internal retrospective to understand the incident in more detail and will share findings within 14 days. Once we complete our internal retrospective, generally within 14 days, we will publish a final Post Incident Review \(PIR\) to all impacted customers. To get notified when that happens, and/or to stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: [https://aka.ms/ash-alerts](https://aka.ms/ash-alerts) For more information on Post Incident Reviews, refer to [https://aka.ms/AzurePIRs](https://aka.ms/AzurePIRs) The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: [https://aka.ms/AzPIR/Monitoring](https://aka.ms/AzPIR/Monitoring) Finally, for broader guidance on preparing for cloud incidents, refer to [https://aka.ms/incidentreadiness](https://aka.ms/incidentreadiness) **How can we make our incident communications more useful?** You can rate this PIR and provide any feedback using our quick 3-question survey: [https://aka.ms/AzPIR/YKYN-BWZ](https://aka.ms/AzPIR/YKYN-BWZ)

Read the full incident report →

Started Oct 10, 2025, 04:00 PM UTC· resolved Dec 04, 2025, 12:45 PM UTC

1. investigating Oct 10, 2025, 04:00 PM UTC

   We are currently experiencing intermittent functionality issues with NIM. Our engineering team is actively investigating the matter to identify the root cause and implement a resolution. Further updates will be provided as more information becomes available.

2. investigating Oct 13, 2025, 08:08 AM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 15, 2025, 08:47 AM UTC

   We have fixed the issue and we are currently monitoring the environment closely.

4. resolved Dec 04, 2025, 12:45 PM UTC

   The issue has been resolved and everything is functioning normally. Thank you for your patience and understanding.

Read the full incident report →

Started Oct 09, 2025, 05:01 PM UTC· resolved Dec 04, 2025, 12:44 PM UTC

1. identified Oct 09, 2025, 05:01 PM UTC

   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.

2. resolved Dec 04, 2025, 12:44 PM UTC

   The issue has been resolved and everything is functioning normally. Thank you for your patience and understanding.

Read the full incident report →

Started Oct 08, 2025, 09:31 AM UTC· resolved Oct 08, 2025, 07:49 PM UTC

1. investigating Oct 08, 2025, 09:31 AM UTC

   The team are currently investigating an issue relating to uploading File Server activity.

2. identified Oct 08, 2025, 01:10 PM UTC

   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.

3. resolved Oct 08, 2025, 07:49 PM UTC

   A fix for this issue is now available in agent v2.0.883.

Read the full incident report →

Started Sep 22, 2025, 09:00 AM UTC· resolved Oct 09, 2025, 04:46 PM UTC

1. investigating Sep 22, 2025, 09:00 AM UTC

   We are currently experiencing intermittent issues with NIM. Our engineering team is actively investigating the matter to identify the root cause and implement a resolution. Further updates will be provided as more information becomes available.

2. investigating Sep 29, 2025, 04:50 PM UTC

   The engineering team are continuing to investigate the cause of the intermittent issue in the France region. Further updates will be provided as more information becomes available.

3. identified Oct 01, 2025, 01:20 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Oct 07, 2025, 08:24 AM UTC

   A fix has been deployed and we are currently monitoring the environment closely.

5. resolved Oct 09, 2025, 04:46 PM UTC

   The issue has been resolved and everything is functioning normally. Thank you for your patience and understanding.

Read the full incident report →

Started Mar 26, 2025, 12:08 PM UTC· resolved May 21, 2025, 04:17 PM UTC

1. identified Mar 26, 2025, 12:08 PM UTC

   We have identified a delay in the import of activity records in the US region. The team have identified the cause and are working on a resolution.

2. identified Mar 31, 2025, 09:03 AM UTC

   We are continuing to work on a fix for this issue.

3. identified Apr 07, 2025, 02:40 PM UTC

   We've stabilized the service and restored full operations for live activity data. We identified that the service had dropped activity events and it is now processing these older events from the import queue. We are monitoring this process and anticipate it completing in the next few days. We will provide another update on the progress of importing the older events within 48 hours.

4. identified Apr 09, 2025, 02:00 PM UTC

   The overall state of activity record imports in both environments has improved. We are continuing to monitor and tune performance as needed to resume normal service.

5. identified Apr 10, 2025, 02:05 PM UTC

   Historical Activity records have now been imported in the EU instance and normal service has now resumed. We will continue to monitor this environment closely to ensure its stability. The US environment is continuing to improve and we will provide an update as soon as this is complete.

6. monitoring Apr 11, 2025, 02:21 PM UTC

   Historical Activity records have now been imported in the US instance. Normal service has now resumed in both the EU and US. We will continue to monitor closely.

7. resolved May 21, 2025, 04:17 PM UTC

   The team have been monitoring the activity feed closely over the past few weeks to validate the resolution of this issue and alerts are being recalculated to include the impacted activity records. Customers are advised to review the alerts dashboard to check for any alerts that require additional action. The team will continue to monitor the feed and are deploying additional automation to improve scaling response times to better meet the highly variable rate of data ingestion.

Read the full incident report →

Started Mar 18, 2025, 01:41 PM UTC· resolved Mar 24, 2025, 01:28 PM UTC

1. investigating Mar 18, 2025, 01:41 PM UTC

   We have identified an issue around SQL queries execution time. We have temporarily increased the allocated resources to reduce the impact. The issue is currently being investigated.

2. monitoring Mar 20, 2025, 02:31 PM UTC

   The issue has been identified. We have taken the necessary steps to mitigate it and we are currently monitoring the SQL performance.

3. resolved Mar 24, 2025, 01:28 PM UTC

   The SQL Performance issue previously encountered has been resolved and everything is functioning normally. Thank you for your patience and understanding.

Read the full incident report →

Started Jan 29, 2025, 11:36 AM UTC· resolved Jan 29, 2025, 03:27 PM UTC

1. identified Jan 29, 2025, 11:36 AM UTC

   We have identified an issue around executing actions on a workflow. A fix is currently being rolled out and we will provide an update as soon as it is available.

2. monitoring Jan 29, 2025, 01:18 PM UTC

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

3. resolved Jan 29, 2025, 03:27 PM UTC

   The fix has been validated and this issue is now resolved.

Read the full incident report →