This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Tuesday, 04 February 2020 01:54 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/04, 01:40 UTC. Our logs show the incident started on 02/03, 21:31 UTC and that during the 4 hours 9 minutes hours that it took to resolve the issue, some customers in West US, WestUS2, East US and South Central US experienced Data Latency, data gaps and incorrect alert activation.
-Subhash
We've confirmed that all systems are back to normal with no customer impact as of 02/04, 01:40 UTC. Our logs show the incident started on 02/03, 21:31 UTC and that during the 4 hours 9 minutes hours that it took to resolve the issue, some customers in West US, WestUS2, East US and South Central US experienced Data Latency, data gaps and incorrect alert activation.
- Root Cause: The failure was due to one of the dependent service.
- Incident Timeline: 4 Hours & 9 minutes - 02/03, 21:31 UTC through 02/04, 01:40 UTC
-Subhash
Initial Update: Monday, 03 February 2020 23:53 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers in West US 2 and East US may experience Data Latency,data gaps and incorrect alert activation.
-Subhash
We are aware of issues within Application Insights and are actively investigating. Some customers in West US 2 and East US may experience Data Latency,data gaps and incorrect alert activation.
- Work Around:
- Next Update: Before 02/04 04:00 UTC
-Subhash