This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Sunday, 05 April 2020 09:07 UTC
We've confirmed that all systems are back to normal with no customer impact as of 04/05, 07:20 UTC. Our logs show the incident started on 04/05, 03:55 UTC and that during the 3 hours 25 minutes that it took to resolve the issue some customers might have experienced intermittent data latency, data gaps and incorrect alert activation in the East US region.
-Syed
We've confirmed that all systems are back to normal with no customer impact as of 04/05, 07:20 UTC. Our logs show the incident started on 04/05, 03:55 UTC and that during the 3 hours 25 minutes that it took to resolve the issue some customers might have experienced intermittent data latency, data gaps and incorrect alert activation in the East US region.
- Root Cause: The failure was because of one of our dependent service.
- Incident Timeline: 3 Hours & 25 minutes - 04/05, 03:55 UTC through 04/05, 07:20 UTC
-Syed
Initial Update: Sunday, 05 April 2020 06:52 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers using Application Insights in East US region may experience intermittent data latency, data gaps and incorrect alert activation.
-Mohini
We are aware of issues within Application Insights and are actively investigating. Some customers using Application Insights in East US region may experience intermittent data latency, data gaps and incorrect alert activation.
- Work Around: None
- Next Update: Before 04/05 11:00 UTC
-Mohini