Final Update: Monday, November 13th 2017 14:23 UTC
We’ve confirmed that all systems are back to normal as of 11/13/2017 12:35 UTC. Our logs show the incident started on 11/13/2017 12:10 and that during the 25 minutes that it took to resolve the issue. Customers experienced slow and failed commands within the UI in the Western Europe region. Sorry for any inconvenience this may have caused.
- Root Cause: We have collected diagnostic data and continue to actively investigate the issue.
- Chance of Re-occurrence: High
- Lessons Learned: We are working both minimizing resource-intensive activities in our post-deployment steps, and are also working targeting monitors specifically to detect post-deployment issues in the future.
- Incident Timeline: 25 minutes – 11/13/2017 12:10 UTC through 11/13/2017 12:35 UTC
Sincerely,
Randy
Initial Update: Monday, November 13th 2017 12:39 UTC
- We're actively investigating error and performance degradation while using Visual Studio Team Services web site in West Europe.
- Our telemetry shows that some users might see HTTP errors (503) as well as the slow rendering of the various Visual Studio Team Services web pages.
Next Update: Before Monday, November 13th 2017 14:00 UTC
Sincerely,
Olivier Dovelos
This post first appeared on MSDN Blogs | Get The Latest Information, Insights, Announcements, And News From Microsoft Experts And Developers In The MSDN Blogs., please read the originial post: here
