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 in our South Brazil Region, and are sorry for any inconvenience you may have experienced. We will be continuing to investigate this issue further so that it does not occur again. Thank you for your patience.

• Work Around: None
• Next Update: Before 28 March 2017 22:00 UTC

Sincerely,
Dexter

Update: Tuesday, 28 March 2017 00:27 UTC

Our DevOps team continues to investigate issues with related to the slow performance. Root cause is not fully understood at this time, though it is suspected to be a regression in SQL query performance for some commands. Some customers continue to experience slow commands in the South Brazil region, though we are no longer seeing significant widespread impact. The problem began at 27 March 2017 ~20:00 UTC. We currently have no estimated time for resolution.

• Work Around: None
• Next Update: Before 02:30 UTC

Sincerely,
Dexter

Initial Update: Monday, 27 March 2017 23:30 UTC

We are actively investigating issues with VSTS in the South Brazil Region. Some customers may experience slow performance when accessing their accounts.

• Next Update: Before Tuesday, 28 March 00:30 UTC

Sincerely,
Colin