Deploy consistently failing

[PaulS]

I seem to be having random deploy errors. This error happened a few times randomly yesterday and has now been happening consistently since last night. Pretty new to fly.io.

Error: release command failed - aborting deployment. error running release_command machine: timeout reached waiting for machine's state to change
Your machine never reached the state "stopped".

I also tried a 10 min wait timeout for the deploy with the same result.

I tried also tried to delete the release_command machine and got:

Error: could not destroy machine d8d9223f172048: failed to destroy VM d8d9223f172048: request returned non-2xx status, 408 (Request ID: 01J7B7NFYCTK79ZJ8YTCN0Q20X-iad)

Any thoughts or help would be appreciated.

[greg]

Hi,

It looks there may be an issue.

It’s not entirely clear if it’s regional, since some regions seem fine. There seem to be multiple people currently finding deploy/scale issues from this thread:

Anyone else having their apps go down?

There is an issue with a host that a machine of my app is on, and it seemed to have rendered the whole app useless. I’m trying to move the machine to a different host, but whatever I try I get errors in the flyctl. Error: could not start machine XYZ: failed to start VM XYZ: request returned non-2xx status, 408 (Request ID: XYZ-ams) Error: failed to get volume: failed to get volume vol_XYZ: request returned non-2xx status, 408 (Request ID: XYZ-syd) On fly scale count I get: Oops, something we…

Hopefully the status page or that thread will be updated.