Final Update: Wednesday, August 9th 2017 18:15 UTC
We’ve confirmed that all systems are back to normal as of 18:00 UTC. We have forced a fail over of the database which has mitigated the issue. All necessary logs have been collected and we are closely working with our partners in SQL Azure to root cause this problem and avoid recurrence.
Update: Wednesday, August 9th 2017 17:37 UTC
We have been able to isolate the incident to a database in one of our West European scale units which is being upgraded at the moment. A subset of users with their VSTS accounts hosted on this impacted database may notice errors and degraded performance while performing interactive actions. We continue to investigate this and will provide an update in the next hour.
- Next Update: Before Wednesday, August 9th 2017 18:45 UTC
Initial Update: Wednesday, August 9th 2017 17:06 UTC
A potentially customer impacting alert is being investigated. Triage is in progress and we will provide an update with more information.
- Next Update: Before Wednesday, August 9th 2017 18:15 UTC