Performance issues with Visual Studio Team Services in South Brazil Region – 03/27 – Resolved

Update: Tuesday, 28 March 2017 02:01 UTC Root cause is believed to be to post-deployment SQL steps which were impacting the performance across a wide set of features. The problematic SQL statements completed at 27 March 2017 18:35 UTC and the service is now working as expected. We do not expect any residual issue from this incident for customers…


Connectivity issues with Visual Studio Team Services – 03/27 – Resolved

Update: Monday, 27 March 2017 10:45 UTC The service is healthy now. Following Visual Studio Team Services(VSTS) offerings via Azure Ibiza Portal (portal.azure.com ) were inaccessible to customers for a period of ~4hrs (6:08 UTC – 10:15 UTC): Team Services Accounts Team Projects Load Testing Continuous Delivery (Release Management) The cause of the issue has…


Login issues with Visual Studio Team Services – 03/24 – Resolved

Update: Saturday, 25 March 2017 00:30 UTC Azure Active directory team applied a mitigation to restore the Microsoft login service. Visual Studio Team Services login and account related features are now working as expected. We are working with our internal partner team to understand root cause and implement steps to avoid this issue in the…


Login issues with Visual Studio Team Services – 03/21 – Resolved

Update: Tuesday, 21 March 2017 20:17 UTC A fix has been deployed to restore the Microsoft login service. Visual Studio Team Services login and account related features are now working as expected. We are working with our internal partner team to understand root cause and implement steps to avoid this issue in the future. Next Update:…


Signin flow changes on Visual Studio Team Services – ADVISORY

We have recently implemented a change to the way users of Visual Studio Team Services sign in and sign out of our service.  The vast majority of users should see no impact from this change but we have found that some customers may experience issues signing into the product due to group policy based security…


Issues with Package Management in Visual Studio Team Services – 03/17 – Resolved

Update: Saturday, 18 March 2017 03:05 UTC We completed our investigation and we didn’t see any customer impact during this issue. We posted our initial communication as a caution after we saw an increase in operation cancelled exceptions. We did the further investigation and didn’t see any impact to customers due to these exceptions.  Sincerely,Bapayya Update:…


Issues with Pull Requests on Visual Studio Team Services – 03/17 – Mitigated

Update: Saturday, 18 March 2017 21:34 UTC We are providing additional details on workaround steps so that users can apply the mitigation steps based on the issues they are seeing for pull requests. We see that during yesterday’s incident some of our jobs that perform merges failed and left some pull requests in this state. We resolved…


Performance issues with Visual Studio Team Services – 03/16 – Resolved

Update: Thursday, 16 March 2017 06:04 UTC Our service is now healthy and customers are no longer experiencing degraded performance.   A configuration issue in the underlying network infrastructure affected a single web-role, in our central Shared Platform Service (SPS), which introduced high network latency. As a result about 10% of SPS calls experienced slowness….


Long Build queue times on Visual Studio Team Services Hosted Build – 03/15 – Resolved

Update: Thursday, 16 March 2017 00:53 UTC This incident has been mitigated after our partners in Azure have fixed the underlying Storage issue. More details on the primary Storage incident can be found here: https://azure.microsoft.com/en-us/status/history. Users of VS Team Services Hosted Build and Cloud Load Testing would have noticed impact between 15 March 2017 22:42 UTC…


Sign In issues with Visual Studio Team Services – 03/14 – Resolved

Update: Tuesday, 14 March 2017 04:22 UTC The root cause for this incident has been isolated to an issue with an incomplete deployment rollback which caused the requests to be misdirected to a staging slot.  This deployment rollback began at 2017/03/13 22:15 UTC.  We mitigated the issue by swapping back to the previous deployment and…