Jaa

issues with Visual Studio Team Services - 8/31 - Resolved

  • Artikkeli

Final Update: Wednesday, 31 August 2016 06:55 UTC
We've confirmed that all systems are back to normal with no customer impact as of . Our logs show the incident started on  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:
  • Lessons Learned: f there is chance of re-occurrence talk to the specifics on how we'll resolve and plan to monitor & respond while risk is activeTalk to the learning that we pulled out of this incident and will apply to avoid these failure types in the future
  • Incident Timeline:  22:30

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

Final Update: Wednesday, 31 August 2016 06:15 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,

Initial Update: Wednesday, 31 August 2016 06:13 UTC
We are actively investigating issues with Marketplace. Some customers may experience slowness.

  • Work Around: None
  • Next Update: Before 23:00

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

Zainu