This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Tuesday, 22 October 2019 20:32 UTC
We've confirmed that all systems are back to normal with no further customer impact as of 10/22, 17:17 UTC. Our logs show the incident started on 10/22, 17:39 UTC and that during the 22 minutes that it took to resolve the issue X% of customers experienced possible data latency, data loss and difficulty accessing data.
-Jack Cantwell
We've confirmed that all systems are back to normal with no further customer impact as of 10/22, 17:17 UTC. Our logs show the incident started on 10/22, 17:39 UTC and that during the 22 minutes that it took to resolve the issue X% of customers experienced possible data latency, data loss and difficulty accessing data.
- Root Cause: The failure was due to a failure in a back end service.
- Incident Timeline: 22 minutes - 10/22, 17:17 UTC through 10/22, 17:39 UTC
-Jack Cantwell