Final Update: Thursday, 21 February 2019 09:03 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/21, 05:46 UTC. Our logs show the incident started on 02/20, 09:15 UTC and that during the 20 hours & 31 minutes that it took to resolve the issue customers would have experienced alerting issue where notifications are not received.
-Naresh
We've confirmed that all systems are back to normal with no customer impact as of 02/21, 05:46 UTC. Our logs show the incident started on 02/20, 09:15 UTC and that during the 20 hours & 31 minutes that it took to resolve the issue customers would have experienced alerting issue where notifications are not received.
- Root Cause: The failure was due to deployment within Azure Monitor environment.
- Incident Timeline: 20 Hours & 31 minutes - 02/20, 09:15 UTC through 02/21, 05:46 UTC
-Naresh
Update: Thursday, 21 February 2019 03:34 UTC
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience alerting issue where email is not received.
- Next Update: Before 02/21 06:00 UTC
Initial Update: Thursday, 21 February 2019 00:29 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers might not have received alerting emails even though the alert is in active state. We provide more updates as we learn.
-Jayadev
We are aware of issues within Log Analytics and are actively investigating. Some customers might not have received alerting emails even though the alert is in active state. We provide more updates as we learn.
- Next Update: Before 02/21 02:30 UTC
-Jayadev
Updated Feb 21, 2019
Version 3.0Azure-Monitor-Team
Former Employee
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity