Final Update: Thursday, 18 April 2019 21:25 UTC
We've confirmed that all systems are back to normal with no customer impact as of 4/18, 20:25 UTC.
-Matthew Cosner
We've confirmed that all systems are back to normal with no customer impact as of 4/18, 20:25 UTC.
- Root Cause: The failure was due to a dependent service used for email communication which entered an unhealthy state.
- Lessons Learned: We will be following up to understand how this issue could have been detected and mitigated more quickly.
-Matthew Cosner
Update: Thursday, 18 April 2019 20:14 UTC
Root cause has been isolated to a dependent service which was in an unhealthy state. This service is in the process of rolling back to an earlier build. Some customers may continue to experience alerting delays or failures.
Root cause has been isolated to a dependent service which was in an unhealthy state. This service is in the process of rolling back to an earlier build. Some customers may continue to experience alerting delays or failures.
- Work Around: Email notifications configured to send directly to an email address are not impacted.
- Next Update: Before 04/18 22:30 UTC
Initial Update: Thursday, 18 April 2019 18:54 UTC
We are aware of issues with email notifications either failing to be sent or being delayed. This impact includes some subset of customers using classic alert emails, daily cap email notifications, smart detection email notifications, and availability test email notifications configured to send to subscription admins, contributors, or readers. Other notification flows such as webhooks are not impacted. Informational notifications were also sent to affected subscriptions through the Azure portal.
-Matthew Cosner
We are aware of issues with email notifications either failing to be sent or being delayed. This impact includes some subset of customers using classic alert emails, daily cap email notifications, smart detection email notifications, and availability test email notifications configured to send to subscription admins, contributors, or readers. Other notification flows such as webhooks are not impacted. Informational notifications were also sent to affected subscriptions through the Azure portal.
- Work Around: Email notifications configured to send directly to an email address are not impacted.
- Next Update: Before 04/18 20:00 UTC
-Matthew Cosner
Updated Apr 18, 2019
Version 4.0Azure-Monitor-Team
Microsoft
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity