Jaa

Test - 8/22 - Investigating

  • Artikkeli

Update: Monday, 22 August 2016 17:50 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,
<%=UserName%>

Final Update: Monday, 22 August 2016 17: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 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,
<%=UserName%>

Update: Monday, 22 August 2016 17:48 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,
<%=UserName%>

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