Final Update: Monday, 17 August 2020 17:05 UTC
We've confirmed that all systems are back to normal with no customer impact as of 8/17, 16:44 UTC. Our logs show the incident started on 8/17, 13:16 UTC and that during the 3 hours and 28 minutes that it took to resolve the issue 50 customers globally experienced up to 3 hours of latency in seeing confirmation of fired alerts in the Azure portal.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 8/17, 16:44 UTC. Our logs show the incident started on 8/17, 13:16 UTC and that during the 3 hours and 28 minutes that it took to resolve the issue 50 customers globally experienced up to 3 hours of latency in seeing confirmation of fired alerts in the Azure portal.
- Root Cause: The failure was due to a dependent backend service node going into a bad state causing the alerting service to be unable to report the fired alert resulting in the portal being unable to retrieve it.
- Incident Timeline: 3 Hours & 28 minutes - 8/17, 13:16 UTC through 8/17, 16:44 UTC
-Jeff
Initial Update: Monday, 17 August 2020 16:58 UTC
We are aware of issues within Metric Alerts and are actively investigating. Some customers may experience latency in seeing confirmation of fired alerts in the Azure portal. The alerts will fire as normal, but there may be a latency of up to 3 hours in presentation of the alert in the portal.
-Jeff
We are aware of issues within Metric Alerts and are actively investigating. Some customers may experience latency in seeing confirmation of fired alerts in the Azure portal. The alerts will fire as normal, but there may be a latency of up to 3 hours in presentation of the alert in the portal.
- Next Update: Before 08/17 19:00 UTC
-Jeff
Updated Aug 17, 2020
Version 2.0