This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Saturday, 25 January 2020 00:09 UTC
We've confirmed that all systems are back to normal with no customer impact as of 1/24, 22:15 UTC. Our logs show the incident started on 1/24, 21:30 UTC and that during the 45 min that it took to resolve the issue customers in multiple regions experienced data latency, data gaps and incorrect alert activation.
-Anupama
We've confirmed that all systems are back to normal with no customer impact as of 1/24, 22:15 UTC. Our logs show the incident started on 1/24, 21:30 UTC and that during the 45 min that it took to resolve the issue customers in multiple regions experienced data latency, data gaps and incorrect alert activation.
- Root Cause:The failure was due to one of the dependent services becoming unhealthy.
- Incident Timeline: 45 minutes - 1/24, 21:30 UTC through 1/24, 22:15 UTC
-Anupama
Initial Update: Friday, 24 January 2020 22:34 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers in multiple regions may experience data latency, data gaps and incorrect alert activation.
-Anupama
We are aware of issues within Application Insights and are actively investigating. Some customers in multiple regions may experience data latency, data gaps and incorrect alert activation.
- Work Around: None
- Next Update: Before 01/25 02:00 UTC
-Anupama