Update: Thursday, 16 March 2017 03:53 UTC
The investigation is still underway. Root cause is not fully understood at this time. Some customers continue to experience Performance Issues accessing the service.
Investigation is currently focused on Source Network Address Translation ports that are being exhausted due to an increase in number of outbound connections we have been making within our service to service calls. We currently have no estimated time for resolution.
- Next Update: Before 06:00 UTC
Update: Thursday, 16 March 2017 02:45 UTC
We continue to investigate the incident. The issue has been isolated to slow calls to our central Shared Platform Service. Our partners in Azure are engaged and are assisting in mitigation efforts.
Our telemetry indicates that the issue started at 23:30 UTC on 15 March 2017 and is impacting ~7% of active users. Users would notice intermittent performance issues and suboptimal page load times accessing the service.
- Next Update: Before 04:00 UTC
Initial Update: Thursday, 16 March 2017 01:27 UTC
We are actively investigating performance issues with Visual Studio Team Services. Some customers may experience slower than usual performance while accessing their VS Team Services accounts.
- Next Update: Before 02:30 UTC
This post first appeared on MSDN Blogs | Get The Latest Information, Insights, Announcements, And News From Microsoft Experts And Developers In The MSDN Blogs., please read the originial post: here