Developers trying to create apps or machines, including during deployments, may have encountered “no capacity available in <region>" errors today. We deployed a change to flyd at 18:51 UTC and rolled it back at 19:25 UTC. That change included an occasional bug in how we calculate host capacity, which for some developers resulted in the "no capacity available in <region>" errors.
Please retry any deployments or machine creations that failed during this time.
No components marked as affected
Resolved
Developers trying to create apps or machines, including during deployments, may have encountered “no capacity available in <region>" errors today. We deployed a change to flyd at 18:51 UTC and rolled it back at 19:25 UTC. That change included an occasional bug in how we calculate host capacity, which for some developers resulted in the "no capacity available in <region>" errors.
Please retry any deployments or machine creations that failed during this time.