Flyctl List shows two VM’s per region, rather than having an instance in each region.
App Name = name Owner = name Version = 12 Status = running Hostname = name.fly.dev Deployment Status ID = Version = v12 Status = successful Description = Deployment completed successfully Instances = 6 desired, 6 placed, 6 healthy, 0 unhealthy flyctl Instances ID VERSION REGION DESIRED STATUS HEALTH CHECKS RESTARTS CREATED 2d383ff9 12 ord run running 1 total, 1 passing 0 7m29s ago a061e8dd 12 ord run running 1 total, 1 passing 0 7m59s ago 0d41ccbe 12 sea run running 1 total, 1 passing 0 8m8s ago 5931d3ed 12 sea run running 1 total, 1 passing 0 8m46s ago 5a884205 12 atl run running 1 total, 1 passing 0 8m46s ago 923db441 12 atl run running 1 total, 1 passing 0 9m17s ago
Here’s my region pool:
Region Pool: atl ewr iad lax ord sea
Can I force Fly to keep VM’s running in each region?
As an aside, my use case is running a latency benchmark from each edge location. I plan on calling the instance internally with
region.name.fly.dev. If I send a request like that to a region that’s offline, what happens? A 500 error?