Deployment Error: no capacity available

anyone know if there is an issue with deployments? I cannot seem to deploy a docker image to a single region. yyz, yul, ord, iad all fail with the same message:

error creating a new machine: failed to launch VM: no capacity available in iad (Request ID: 01HF7ATTPAFZ1ZJPWX6895Z288-yyz)`

1 Like

Every US/CA region. sjc started to deploy but then also failed:

no capacity available in sjc (Request ID: 01HF7BZ6K6GKFYQXD6XD95MXRJ-yyz)

Hello! We are aware of the issue and it is under investigation. thanks!

great thanks, I had checked status but I guess I was too early. I’ll remove this post.

np! it’s ok to keep it open so we can refer any other posters to it or other users can find it.

1 Like

Hi @Reflectance, we have mitigated the problem. Can you confirm if it is solved on your side?

@dangra Yes I am able to deploy without issue. thanks!

1 Like

@dangra, I am now getting this error today trying to deploy in sjc. Request ID: 01HFA0FWTXJM75D34H0SFM3T41-dfw

Seeing this too in dfw? just now.

✖ Failed: error running release_command machine: error creating a release_command machine: failed to launch VM: no capacity available in dfw
Error: release command failed - aborting deployment. error running release_command machine: error creating a release_command machine: failed to launch VM: no capacity available in dfw (Request ID: 01HFA0XA8BBJYKFQ91KQD6TYP3-dfw)
Try choosing a different region for machine creation

Same. Seeing this on iad as well.

Same. In DFW. Kind of concerning.

It’s probably related to yesterday’s Fly.io Status - Elevated "No capacity available" errors but now in a different region. I do wish these status updates would get a little more descriptive, so we actually know what went wrong. We don’t need a deep dive, but having some level of transparency into why it happened, and what measures were put in place to mitigate it, would be nice.

I don’t really agree for the day-to-day stuff like this. Wouldn’t make a difference for me to know if their FireRiceCracker dooda broke because of a misconfigured WireGuardDog thingy in their core network routing.

Tried cdg and it was the same.

1 Like

also seeing this in a few regions (iad, dfw, gig, sjc, cdg) for at least the last 30 minutes. concerning that there’s nothing acknowledged on https://status.flyio.net/

2 Likes

Getting the same error for both dfw and den. Echoing the concern that the status page doesn’t reflect anything.

1 Like

@rubys any chance you can speak to what’s happening? I’ve had a few project demos I needed to do today and deploying is impossible; why isn’t the status page conveying what’s going on?

Worked now for me in cdg.

Just worked in den as well.

Sorry about that - we have deployed a fix for this. If you’re still seeing no capacity available, can you share what region you are closest to?

curl -s debug.fly.dev | grep -i region

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.