This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Monday, 28 March 2022 01:51 UTC
We've confirmed that all systems are back to normal with no customer impact as of 3/28, 01:20 UTC. Our logs show the incident started on 3/28, 00:40 UTC and that during the 40 minutes that it took to resolve the issue, customers using Log Analytics in Southeast Asia may have experienced issues accessing your data as well as missed or delayed Log Search Alerts.
-Eric Singleton
We've confirmed that all systems are back to normal with no customer impact as of 3/28, 01:20 UTC. Our logs show the incident started on 3/28, 00:40 UTC and that during the 40 minutes that it took to resolve the issue, customers using Log Analytics in Southeast Asia may have experienced issues accessing your data as well as missed or delayed Log Search Alerts.
- Root Cause: The failure was due to a backend dependency.
- Incident Timeline: 40 minutes - 3/28, 00:40 UTC through 3/28, 01:20 UTC
-Eric Singleton