This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
We've
confirmed that all systems are back to normal as of 3/21/22, 00:05 UTC. Our
logs show the incident started on 3/20/22, 22:21 UTC and that during the 1 hour
44 minutes that it took to resolve the issue, customers using Azure Log
Analytics in Australia Southeast may have experienced data access issues as
well as delayed or misfired alerts.
- Root Cause: The failure was due to a backend service that became unhealthy.
- Incident Timeline: 1 Hours & 44 minutes - 3/20/22, 22:21 UTC through 3/21/22, 00:05 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident has caused.