Hi @miker,
Your issue may be related to this change with Fly Registry optimizations we started rolling out earlier today. I’ll investigate our internal logs further, in the meantime I’ve rolled back the change for now, so please try your deploy again and let me know if this fixes your issue. Sorry for the inconvenience!