This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 30 May 2019 06:11 UTC
We've confirmed that all systems are back to normal with no customer impact as of 05/30, 06:11 UTC. Our logs show the incident started on 05/29, 04:20 UTC and that during the 2 hours 10 minutes that it took to resolve the issue ~3% of subscriptions got impacted and experienced data gaps in availability results.
-Sindhu
We've confirmed that all systems are back to normal with no customer impact as of 05/30, 06:11 UTC. Our logs show the incident started on 05/29, 04:20 UTC and that during the 2 hours 10 minutes that it took to resolve the issue ~3% of subscriptions got impacted and experienced data gaps in availability results.
- Root Cause: The failure was due to issue in one of our backend services.
- Incident Timeline: 2 Hours & 10 minutes - 05/29, 04:20 UTC through 05/29, 06:30 UTC
-Sindhu