Final Update: Friday, January 26th 2018 15:21 UTC
We’ve confirmed that all systems are back to normal. We're continuing to investigate why the change was made to ensure this doesn't occur on other DBs.
Update: Friday, January 26th 2018 14:48 UTC
The Engineering team has narrowed down the cause of the slow and failed commands to a change being run on a SQL Azure database. We're working to understand why this occurred.
VSTS Users in West Europe may experience failed and slow commands while using various VSTS features.
- Next Update: Before Friday, January 26th 2018 16:00 UTC
Initial Update: Friday, January 26th 2018 14:33 UTC
We are currently investigating Slow and Failed Commands in West Europe.
- Next Update: Before Friday, January 26th 2018 15:40 UTC