Final Update: Wednesday, 05 June 2019 07:59 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/05, 07:15 UTC. Our logs show the incident started on 06/05, 06:10 UTC and that during the ~1 hour that it took to resolve the issue some customers in the East US2 region experienced issues while accessing their data in the azure portal. Query performance would also have been impacted in this region.
-Varun
We've confirmed that all systems are back to normal with no customer impact as of 06/05, 07:15 UTC. Our logs show the incident started on 06/05, 06:10 UTC and that during the ~1 hour that it took to resolve the issue some customers in the East US2 region experienced issues while accessing their data in the azure portal. Query performance would also have been impacted in this region.
- Root Cause: The failure was due to a configuration issue in one of our backend services.
- Incident Timeline: 1 Hours & 5 minutes - 06/05, 06:10 UTC through 06/05, 07:15 UTC
-Varun
Published Jun 05, 2019
Version 1.0