This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 22 November 2019 17:15 UTC
We've confirmed that all systems are back to normal as of 11/22, 16:58 UTC. Our logs show the incident started on 11/22, 08:23 UTC and that during the 8 hours 35 minutes that it took to resolve the issue 18% of customers in East US region might have encountered error messages when trying to use virtual machine Service Map data in Azure portal.
-Sindhu
We've confirmed that all systems are back to normal as of 11/22, 16:58 UTC. Our logs show the incident started on 11/22, 08:23 UTC and that during the 8 hours 35 minutes that it took to resolve the issue 18% of customers in East US region might have encountered error messages when trying to use virtual machine Service Map data in Azure portal.
- Root Cause: The failure was due to issue in one of our back end services.
- Incident Timeline: 8 Hours & 35 minutes - 11/22, 08:23 UTC through 11/22, 16:58 UTC
-Sindhu
Update: Friday, 22 November 2019 16:32 UTC
Root cause has been isolated to an unhealthy resource which was impacting Service Map data access in East US. The issue is currently being mitigated. The issue is expected to be fully mitigated within the next 3 hours.
Root cause has been isolated to an unhealthy resource which was impacting Service Map data access in East US. The issue is currently being mitigated. The issue is expected to be fully mitigated within the next 3 hours.
- Work Around: None
- Next Update: Before 11/22 19:00 UTC
Update: Friday, 22 November 2019 13:06 UTC
We continue to investigate issues within Service Map. Some customers continue to experience data access issue in East US region. We are working to establish the start time for the issue, initial findings indicate that the problem began at 11/22 ~08:23 UTC.
We continue to investigate issues within Service Map. Some customers continue to experience data access issue in East US region. We are working to establish the start time for the issue, initial findings indicate that the problem began at 11/22 ~08:23 UTC.
- Work Around: None
- Next Update: Before 11/22 17:30 UTC
Initial Update: Friday, 22 November 2019 09:56 UTC
We are aware of issues within Service Map and are actively investigating. Some customers may experience data access issue in East US region.
-Naresh
We are aware of issues within Service Map and are actively investigating. Some customers may experience data access issue in East US region.
- Work Around: None
- Next Update: Before 11/22 13:00 UTC
-Naresh