Final Update: Friday, 07 July 2017 15:15 UTC
We confirmed that all systems are back to normal since Friday, 07 July 2017 06:15 UTC . We have validated redeployed services and our monitoring is healthy as expected. At this moment , we don't have any customer impact and customers should be able to use Service Map without any errors.
Root Cause: The failure was due to a configuration change in one of the back-end platform services.
We understand that customers rely on Service Map as a critical service and apologize for any impact this incident caused.
Update: Friday, 07 July 2017 05:15 UTC
We understand the issue that started Thursday , 06 July 2017 23:55 UTC ; it was due to a recent change in underlying service which is responsible for data access layer. At present we are collecting necessary telemetry for further analysis to avoid similar issue in future. Our mitigation will require redeploy for services again in this region and we expect this to completed and validated in next couple of hours. We don't have an ETA for full recovery but we provide an update as we progress.
Update: Friday, 07 July 2017 03:37 UTC
We are aware that Service Map is experiencing an issue in West Central US region. Customer in this region may experience issue while requesting machines list and other features of Service Map. We are working on root causing the issue and provide more updates as we learn. This issue has only impacted users in West Central US , all other regions are unaffected and services are running as expected.
•Work Around: None
•Next Update: Before 07/07 07:00 UTC