App down in DFW: machine stuck in `created` state, 408 timeouts on every deploy attempt

2

Hi… Forking (i.e., copying) the volume is the recommended workaround in this situation:

https://community.fly.io/t/insufficient-capacity-in-iad/27499/3

That would be fly vol fork --region ord, if you wanted to give Chicago a try again…