This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 17 May 2019 22:02 UTC
We've confirmed that all systems are back to normal with no customer impact as of 5/17, 21:26 UTC. Our logs show the incident started on 5/16, 21:53 UTC and that during the 23 hours 27 minutes that it took to resolve the issue 3% of customers ingesting data with non-retrying SDK's in USGov Virginia region might have experienced data loss.
-Jayadev
We've confirmed that all systems are back to normal with no customer impact as of 5/17, 21:26 UTC. Our logs show the incident started on 5/16, 21:53 UTC and that during the 23 hours 27 minutes that it took to resolve the issue 3% of customers ingesting data with non-retrying SDK's in USGov Virginia region might have experienced data loss.
- Root Cause: The failure was identified due to a stuck node that needed restart.
- Incident Timeline: 23 Hours & 27 minutes - 5/16, 21:53 UTC through 5/17, 21:26 UTC
-Jayadev