Final Update: Wednesday, 01 June 2022 13:42 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/01, 13:20 UTC. Our logs show the incident started on 06/01, 04:00 UTC and that during the 9hours & 20 minutes that it took to resolve the issue, some of the customers might have experienced data latency and potential data loss. This may have caused delayed or misfired alerts in Canada East region.
-Srikanth
We've confirmed that all systems are back to normal with no customer impact as of 06/01, 13:20 UTC. Our logs show the incident started on 06/01, 04:00 UTC and that during the 9hours & 20 minutes that it took to resolve the issue, some of the customers might have experienced data latency and potential data loss. This may have caused delayed or misfired alerts in Canada East region.
- Root Cause: The failure was due to one of our backend dependency.
- Incident Timeline: 9 Hours & 20 minutes - 06/01, 04:00 UTC through 06/01, 13:20 UTC
-Srikanth
Update: Wednesday, 01 June 2022 11:19 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data latency and potential data loss. This may have caused delayed or misfired alerts
in Canada East region.
- Work Around: None.
- Next Update: Before 06/01 17:30 UTC
Updated Jun 01, 2022
Version 4.0