First published on MSDN on Mar 28, 2018

Final Update: Wednesday, 28 March 2018 01:22 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/28 01:22 UTC. Our logs show the incident started on 03/27/2018 21:59 UTC and that during the 3h 33m that it took to resolve the issue, all of the customers who have configured Networking Monitoring Solution would have experienced issues in Fairfax region with no latest data being reflected in the dashboard. Impact was limited to Network Monitoring solution.


Root Cause:   This issue was caused by a configuration change in our services.
Lessons Learned: We understand the issue completely and additional steps have been taken to avoid such occurrences in future.



We understand the customers rely on Network Performance Monitoring as a critical service and apologize for any impact this incident has caused


-Rahim