issues with Visual Studio Team Services - 8/25 - Resolved
Final Update: Thursday, 25 August 2016 19:13 UTC
We've confirmed that all systems are back to normal with no customer impact as of <DD MonthName YYYY ~HH:MM UTC>. Our logs show the incident started on <DD MonthName YYYY ~HH:MM UTC> and that during the <duration of incident> hours that it took to resolve the issue X% of customers experienced <impact statement & metrics>.
- We understand that customers rely on VS Team Services as a critical service and apologize for any impact this incident caused.
- Sincerely,
- Zainu
Update: Thursday, 25 August 2016 19:12 UTC
Our DevOps team continues to investigate issues with <feature>. Root cause is not fully understood at this time. Some customers continue to experience <impact statement from a user perspective>. We are working to establish the start time for the issue, initial findings indicate that the problem began at <DD MonthName YYYY ~HH:MM UTC>. We currently have no estimated time for resolution.
- Work Around: <none or details>
- Next Update: Before HH:MM UTC
Sincerely,
Zainu