This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 12 March 2020 21:34 UTC
We've confirmed that all systems are back to normal with no customer impact as of 3/12 20:56 UTC. Our logs show the incident started on 3/12, 20:23 UTC and that during the 33 minutes that it took to resolve the issue 10% of customers experienced unexpected query failures, slightly latent data ingestion, and possible misfired alerts.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 3/12 20:56 UTC. Our logs show the incident started on 3/12, 20:23 UTC and that during the 33 minutes that it took to resolve the issue 10% of customers experienced unexpected query failures, slightly latent data ingestion, and possible misfired alerts.
- Root Cause: The failure was due to a backend update process that took longer than expected to complete.
- Incident Timeline: 33 minutes - 3/12, 20:23 UTC through 3/12, 20:56 UTC
-Jeff