Final Update: Friday, 29 July 2016 19:55 UTC

We’ve confirmed that all systems are back to normal with as of 29 July 2016 ~19:14 UTC. Our logs show the Incident started on 29 July 2016 ~17:40 UTC. Configuration changes were made to the backend processes to mitigate this incident. Root cause is being actively investigated.

We understand that customers rely on VS Team Services as a critical service and apologize for any impact this incident caused.

Sincerely,
Sri Harsha

Update: Friday, 29 July 2016 19:04 UTC

The incident is now partially mitigated after a feature flag was disabled.  All the core scenarios should now be working fine, but the admin scenarios are still affected for a sub set of users. Users are advised to retry their operations should you notice any errors.  Account administrators may continue to face errors when modifying settings (e.g. Security memberships).

• Next Update: Before 20:00 UTC

Sincerely,
Sri Harsha

We are actively investigating performance and availability issues with Visual Studio Team Services in multiple geo locations. Some customers may experience issues accessing their Team Services accounts.

• Next Update: Before 19:00 UTC

We are working to resolve this issue and apologize for any inconvenience.

Sincerely,
Sri Harsha