Final Update: Saturday, 18 June 2022 18:34 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/18, 18:05 UTC. Our logs show the incident started on 6/18, 17:25 UTC and that during the30 mins that it took to resolve the issue 11% of customers experienced issues accessing your data as well as missed or delayed alerts
-Robin Paul
We've confirmed that all systems are back to normal with no customer impact as of 6/18, 18:05 UTC. Our logs show the incident started on 6/18, 17:25 UTC and that during the30 mins that it took to resolve the issue 11% of customers experienced issues accessing your data as well as missed or delayed alerts
- Root Cause: The failure was due to a transient issue in a backend service which was self healed by the Azure platform
- Incident Timeline: 30 minutes - 6/18, 17:25 UTC through 6/18, 18:05 UTC
-Robin Paul
Initial Update: Saturday, 18 June 2022 18:14 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues accessing your data as well as missed or delayed alerts.
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues accessing your data as well as missed or delayed alerts.
- Next Update: Before 06/18 20:30 UTC
-Robin Paul
Updated Jun 18, 2022
Version 2.0
Azure-Monitor-Team
Microsoft
Microsoft
