Jaa

Performance issues with Visual Studio Team Services - 8/21 - Resolved

  • Artikkeli

testing

testing

testing new one recent

test new update

tet

testing

done

Its finally resolved

New resolution

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>.

Its finally resolved

Final Update: Sunday, 21 August 2016 15:49 UTC
We've confirmed that all systems are back to normal with no customer impact as of <DD MonthName YYYY ~HH:MM UTC>. Our
We understand that customers rely on VS Team Services as a critical service and apologize for any impact this incident caused.
Sincerely,
<%=UserName%>

Final Update: Sunday, 21 August 2016 15:46 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>.

  • Root Cause: The failure was due to <provide a transparent failure statement but don't mention specific technologies>.
  • Chance of Reoccurrence: <List out the probability that this will re-occur>
  • Lessons Learned: <if there is chance of re-occurrence talk to the specifics on how we'll resolve and plan to monitor & respond while risk is active><Talk to the learning that we pulled out of this incident and will apply to avoid these failure types in the future>
  • Incident Timeline: <X Hours> & <X minutes> - <DD MonthName YYYY ~HH:MM UTC> through <DD MonthName YYYY ~HH:MM UTC>

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

Final Update: Sunday, 21 August 2016 12:20 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>.

  • Root Cause: The failure was due to <provide a transparent failure statement but don't mention specific technologies>.
  • Chance of Reoccurrence: <List out the probability that this will re-occur>
  • Lessons Learned: <if there is chance of re-occurrence talk to the specifics on how we'll resolve and plan to monitor & respond while risk is active><Talk to the learning that we pulled out of this incident and will apply to avoid these failure types in the future>
  • Incident Timeline: <X Hours> & <X minutes> - <DD MonthName YYYY ~HH:MM UTC> through <DD MonthName YYYY ~HH:MM UTC>

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

Update: Sunday, 21 August 2016 12:12 UTC
Our DevOps team continues to investigate issues with Hosted build. Root cause is not fully understood at this time. Some customers continue to experience Some customers may experience build queues getting slow.We are working to establish the start time for the issue, initial findings indicate that the problem began at  21 Aug 2016~10:30UTC . We currently have no estimated time for resolution.

  • Work Around: None
  • Next Update: Before 14:00UTC

Sincerely,
Zainu

.
Initial Update: Sunday, 21 August 2016 12:06 UTC
We are actively investigating issues with Hosted Build. Some customers may experience build queues getting slow.

  • Work Around: None
  • Next Update: Before  14:00 UTC

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