Resolved -
We are continuing to work with our cloud partner to investigate the root cause of the incident.
All VM services are now fully operational.
Apr 10, 21:25 UTC
Monitoring -
Our cloud partner has identified and resolved the issue within their service.
We are actively monitoring the situation.
Apr 10, 21:04 UTC
Update -
Our cloud partner has identified and resolved the issue within their service. We are continuing to process a backlog log jobs delayed by this issue.
Apr 10, 20:50 UTC
Update -
We are currently processing a backlog of jobs currently awaiting allocation on the Machine Executor and for Remote Docker jobs.
We will provide more information shortly.
Apr 10, 20:30 UTC
Update -
We're continuing to work through this issue with our upstream cloud provider, and will continue to provide updates as soon as they are available.
Apr 10, 20:12 UTC
Update -
We're continuing to work through this issue with our upstream cloud provider, and will continue to provide updates as soon as they are available.
Apr 10, 19:52 UTC
Update -
We're continuing to work closely with our cloud provider on this issue, and will provide an update as soon as one is available.
Apr 10, 19:29 UTC
Update -
Our support ticket with our cloud provider has now been escalated to P0. We continue to work fervently toward a resolution.
Apr 10, 19:08 UTC
Update -
We have a P1 ticket open with our cloud providers and are working on a resolution.
Apr 10, 18:55 UTC
Update -
We have identified the cause of this issue and are working on a resolution.
Apr 10, 18:31 UTC
Identified -
We have identified the cause of delayed Machine executor and Remote Docker services.
Apr 10, 18:08 UTC
Investigating -
We are currently investigating delays affecting users utilizing the Machine executor and Remote Docker services.
We will provide updates shortly.
Apr 10, 17:45 UTC