We've confirmed that all systems are back to normal as of 11/19, 21:56 UTC. Our logs show that the incident started on 11/19, 15:35 UTC and that during the 6 hours and 21 minutes that it took to resolve the issue some of the customers using Azure Log Analytics might have experienced data gaps, partial query results and incorrect alerts activation in Australia Central2 region.
Root Cause: The failure was due to a recent configuration change in one of our backend services.
Incident Timeline: 6 Hours & 21 minutes - 11/19, 15:35 UTC through 11/19, 21:56 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.