Final Update: Wednesday, 14 October 2020 00:02 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/13, 23:43 UTC. Our logs show the incident started on 10/13, 23:07 UTC and that during the 36 minutes that it took to resolve the issue many customers in the East US region experienced data latency and possible data loss.
-Jack Cantwell
We've confirmed that all systems are back to normal with no customer impact as of 10/13, 23:43 UTC. Our logs show the incident started on 10/13, 23:07 UTC and that during the 36 minutes that it took to resolve the issue many customers in the East US region experienced data latency and possible data loss.
- Root Cause: The failure was due to a failed upgrade to a backend service and was fixed when the upgrade was rolled back.
- Incident Timeline: 37 minutes - 10/13, 23:07 UTC through 10/13, 23:43 UTC
-Jack Cantwell
Initial Update: Tuesday, 13 October 2020 23:27 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data latency or data loss.
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data latency or data loss.
- Next Update: Before 10/14 00:30 UTC
-Jack Cantwell
Updated Oct 14, 2020
Version 2.0