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 and 16 March 2017 00:00 UTC.
We’re still working with Azure to fully understand the exact steps that resulted in this issue and how to avoid going forward. We’ll follow-up with a more detailed postmortem as soon as we have it finalized.
Update: Wednesday, 15 March 2017 23:48 UTC
We are closely working with our partners in Azure to investigate an upstream problem with Storage that is impacting Hosted Build service. More details about this incident can be found at https://status.azure.com.
Hosted Build customers will continue to notice long build queue times and failures.
- Next Update: Before 16 March 2017 01:00 UTC
Initial Update: Wednesday, 15 March 2017 22:54 UTC
We are actively investigating issues with Hosted Build service in VS Team Services in multiple regions. Customers may experience long build queue times and failures.
- Next Update: Before 16 March 2017 00:00 UTC
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