This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Saturday, 14 May 2022 00:27 UTC
We've confirmed that all systems are back to normal with no customer impact as of 05/13 23:45 UTC. Our logs show the incident started on 05/13 22:52 UTC and that during the 53 minutes that it took to resolve the issue some customers using Log Analytics in North Central US may have experienced issues with accessing data as well as missed or delayed alerts.
We've confirmed that all systems are back to normal with no customer impact as of 05/13 23:45 UTC. Our logs show the incident started on 05/13 22:52 UTC and that during the 53 minutes that it took to resolve the issue some customers using Log Analytics in North Central US may have experienced issues with accessing data as well as missed or delayed alerts.
- Root Cause: The failure was due to issues with one of the backend service.
- Incident Timeline: 53 minutes - 05/13 22:52 UTC through 05/13 23:45 UTC
-Jayadev
Initial Update: Friday, 13 May 2022 23:41 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics in North Central US may experience issues with accessing data as well as missed or delayed alerts. Initial Investigation suggests that issue started at around 5/13 22:52 UTC.
-Jayadev
We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics in North Central US may experience issues with accessing data as well as missed or delayed alerts. Initial Investigation suggests that issue started at around 5/13 22:52 UTC.
- Next Update: Before 05/14 04:00 UTC
-Jayadev