Share via

Issues with Visual Studio Team Services - 04/27 - Investigating

  • Article

Update: Wednesday, May 24th 2017 18:41 UTC

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

  • Work Around: none
  • Next Update: Before Wednesday, May 24th 2017 20:45 UTC

Sincerely,
Rama Subba Rao

Update: Monday, May 15th 2017 19:16 UTC

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

  • Work Around: none
  • Next Update: Before Monday, May 15th 2017 21:30 UTC

Sincerely,
Rama Subba Rao

Final Update: Saturday, May 13th 2017 23:07 UTC

Our DevOps team continues to investigate issues with . Root cause is not fully understood at this time, though it is suspected to be . The problem began at . We currently have no estimated time for the next that solution.

  • Work Around: None
  • Next Update: Before Sunday, May 14th 2017 01:15 UTC

Sincerely,
Rama Subba Rao

Update: Saturday, May 13th 2017 23:02 UTC

Our DevOps team continues to investigate issues with . Root cause is not fully understood at this time, though it is suspected to be . The problem began at . We currently have no estimated time for the next solution.

  • Work Around: None
  • Next Update: Before Sunday, May 14th 2017 01:15 UTC

Sincerely,
Rama Subba Rao

Update: Saturday, May 13th 2017 02:22 UTC

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

Sincerely,
Rama Subba Rao

Final Update: Saturday, May 13th 2017 02:20 UTC

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

Final Update: Saturday, May 13th 2017 02:07 UTC

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

Sincerely,
Rama Subba Rao

Update: Saturday, May 13th 2017 02:03 UTC

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

Sincerely,
Rama Subba Rao

Final Update: Saturday, May 13th 2017 01:51 UTC

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

  • Root Cause: The failure was due to .
  • 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,
Rama Subba Rao

Update: Saturday, May 13th 2017 01:50 UTC

A potentially customer impacting alert is being investigated testing. Triage is in progress and we will provide an update with more information.

Sincerely,
Rama Subba Rao

Update: Friday, May 12th 2017 15:47 UTC

A potentially customer impacting alert is being investigated testing. Triage is in progress and we will provide an update with more information.

Sincerely,
Rama Subba Rao

Initial Update: Thursday, April 27th 2017 06:20 UTC

A potentially customer impacting alert is being investigated. Triage is in progress and we will provide an update with more information.

  • Next Update: Before Thursday, April 27th 2017 07:30 UTC

Sincerely,
Rama Subba Rao