Freigeben über

Performance issues with Visual Studio Team Services - 18/04 - Mitigating

  • Artikel

Final Update: Tuesday, April 18th 2017 21:53 UTC

We’ve confirmed that all systems are back to normal as of IMPACTEND. Our logs show the incident started on 27 March 2017 20:00 UTC and that during the HOURS hours and MINUTES minutes that it took to resolve the issue.PERCENT% of customers experienced IMPACT in the REGION. Sorry for any inconvenience this may have caused.

  • Root Cause: The failure was due to ROOTCAUSE.
  • Chance of Re-occurrence: High/Low/Medium
  • Lessons Learned: We are working both minimizing resource-intensive activities in our post-deployment steps, and are also working targeting monitors specifically to detect post-deployment issues in the future.
  • Incident Timeline: HOURS hours & MINUTES minutes – IMPACTSTART UTC through IMPACTEND

Sincerely,
Tom

Update: Tuesday, April 18th 2017 21:42 UTC

Our DevOps team continues to investigate issues with Impact. Root cause is not fully understood at this time, though it is suspected to be DETAILS. The problem began at now-o-clock. We currently have no estimated time for resolution.

  • Work Around: BLAH
  • Next Update: Before Tuesday, April 18th 2017 23:45 UTC

Sincerely,
Tom

An alert indicating performance issues with the service is being investigated. We are triaging user impact and will provide an update in 20 minutes.

Sincerely,
Tom