Final Update: Wednesday, 28 February 2018 08:51 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/28, 08:50 AM UTC. Our logs show the incident started on 02/28, 03:45 AM UTC and that during the 5 hours and 5 minutes that it took to resolve the issue some customers experienced issues while loading machine list and other features in Service Map Service in Azure and OMS Portal..
-
Root Cause: The failure was due to a configuration change in one of our backend services.
-
Incident Timeline: 5 Hours & 5 minutes - 02/28, 03:45 AM UTC through 02/28, 08:50 AM UTC
We understand that customers rely on Service Map as a critical service and apologize for any impact this incident caused.
-Varun