This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Monday, 18 May 2020 16:24 UTC
We've confirmed that all systems are back to normal with no customer impact as of 05/18, 15:25 UTC. Our logs show the incident started on 05/18, 13:45 UTC and that during the 1 hour 40 minutes that it took to resolve the issue some customers in Central US region may have experienced delayed or missed Log Search alerts.
-Anmol
We've confirmed that all systems are back to normal with no customer impact as of 05/18, 15:25 UTC. Our logs show the incident started on 05/18, 13:45 UTC and that during the 1 hour 40 minutes that it took to resolve the issue some customers in Central US region may have experienced delayed or missed Log Search alerts.
- Root Cause: The failure was due to an issue in one of our dependent services.
- Incident Timeline: 1 hour 40 minutes - 05/18, 13:45 UTC through 05/18, 15:25 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.
-Anmol
Initial Update: Monday, 18 May 2020 15:41 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience delayed or missed Log Search Alerts in Central US region.
-Anmol
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience delayed or missed Log Search Alerts in Central US region.
- Next Update: Before 05/18 18:00 UTC
-Anmol