Experiencing Data Access Issue in Service Map - 02/28 - Resolved

[Azure-Monitor-Team]

First published on MSDN on Feb 28, 2018

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

Update: Wednesday, 28 February 2018 07:27 UTC

We continue to investigate issues within Service Map. Root cause is not fully understood at this time. Some customers continue to experience issues while loading machine list and other features in Service Map Service in Azure and OMS Portal. We are working to establish the start time for the issue, initial findings indicate that the problem began at 02/28 ~03:45 UTC. We currently have no estimate for resolution.

• Work Around: None
• Next Update: Before 02/28 10:30 UTC

-Varun

Initial Update: Wednesday, 28 February 2018 04:50 UTC

We are aware of issues within Service Map and are actively investigating. Some customers may experience issues while loading machine list and other features in Service Map Service in Azure and OMS Portal.

• Work Around:
• Next Update: Before 02/28 07:00 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Arvind