Final Update: Monday, January 15th 2018 10:41 UTC
We've confirmed that all systems are back to normal as of 15 January 2018 09:25 UTC. Our logs show that the incident started on 15 January 2018 08:55 UTC and that during the 30 minutes duration of the incident, customers hosted on our North Central US Region would have experienced slow response times while accessing the service. We received alert for High CPU on one of our collection database which was self mitigated. Our team is actively investigating the root cause for higher CPU load on database to avoid reoccurrence.
We understand that customers rely on VS Team Services as a critical service and apologize for any impact this incident caused.
Initial Update: Monday, January 15th 2018 09:21 UTC
We're investigating performance issues with Visual Studio Team Services in North Central US region. Customers may experience slow and failed commands while using VSTS.
We are actively engaged on this and will provide more information as it becomes available.
- Next Update: Before Monday, January 15th 2018 09:55 UTC