"Insufficient resources" errors creating machines with volumes in IAD

1

Hi Fly team,

We’re hitting “insufficient resources to create new machine with existing volume” errors in IAD when deploying new apps. This is affecting both our staging and production environments.

We’re a vibe coding platform that provisions a Fly app + volume + machine per user project. We are planning to scale up aggressively this year… We need reliable machine provisioning in IAD. :folded_hands:

Two questions:

  1. Is there a current capacity constraint in IAD we should know about?
  2. As we scale, should we be on a dedicated plan or specific org configuration?

Happy to hop on a call. Thanks!

3

@nativestranger just reached out to you privately.

1 Like
4

Recent failed provisioning example:

  • App name: rubyonvibes-58e53d7f
  • Region: IAD
  • Timestamp: 2026-02-28 ~14:05 UTC
  • Machine size: shared-cpu-4x@2048MB (intended — machine failed to create)
  • Volume ID: vol_r1ldx9d935dzqn34
  • Volume size: 20GB (intended)
  • Request ID: 01KJFPNEC85T58K9B84QJ0SF84-iad
  • Trace ID: e776e3cacf78133575c35e68921fa008

Error: insufficient resources to create new machine with existing volume

Additional context: We’re seeing a secondary issue where each failed provisioning retry appears to add 20GB to the volume size rather than reusing the existing 20GB volume. We’re investigating on our side but
wanted to flag it in case it’s contributing to placement failures.

5

Happy to write, I haven’t seen this issue recently. Commenting to keep this thread open, for now. Will continue iterating and testing.

6

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