Final Update: Thursday, October 25th 2018 20:31 UTC
We believe the issue is mitigated.
We've already discussed repair items (on the incident bridge) that should prevent a recurrence and will be filing these against the owning teams shortly.
Sincerely,
Kishore
Update: Thursday, October 25th 2018 19:16 UTC
We have identified the problem and are in the process of rolling out a code fix. The fix has been rolled out to one of the (RM) scale units / rings; the second one is in progress (ETA: 20 mins).
We will update once all is clear.
Sincerely,
Kishore Jalleda
Update: Thursday, October 25th 2018 15:24 UTC
We continue to investigate releases that might not be completed successfully in Central US.
Our Engineering teams have identified the issue and they are working on a code fix.
We currently have no estimated time for resolution.
Next Update: Before Thursday, October 25th 2018 19:30 UTC
Sincerely,
Jeancarlo
Update: Thursday, October 25th 2018 13:28 UTC
We continue to investigate releases that might not be completed successfully in Central US.
We are actively working on mitigation and as of now root cause is not fully understood.
We currently have no estimated time for resolution.
- Next Update: Before Thursday, October 25th 2018 15:30 UTC
Sincerely,
Jeancarlo
Initial notification: Thursday, October 25th 2018 12:20 UTC
We're investigating Releases in South Central US.
We have received reports that releases have been not been completing successfully
Releases may not produce log files
Next Update: Before Thursday, October 25th 2018 12:55 UTC
Sincerely,
Brett