From ee3b757c84f818a6bdbfe2286a167158a6866839 Mon Sep 17 00:00:00 2001 From: Kristin Martin Date: Fri, 31 Jul 2026 17:56:50 +0000 Subject: [PATCH] Correct fly platform regions description on machine placement page The command lists regions and region codes; it no longer reports available capacity per region. --- machines/guides-examples/machine-placement.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/machines/guides-examples/machine-placement.html.md b/machines/guides-examples/machine-placement.html.md index 3e929180ac..d4888a42d6 100644 --- a/machines/guides-examples/machine-placement.html.md +++ b/machines/guides-examples/machine-placement.html.md @@ -14,9 +14,9 @@ Let’s say you run `fly scale count` and tell it to drop 10 machines into `dfw` Most of the time this just works—`dfw` and `iad` are solid bets for region choices. But some regions, like `sjc`, `gru`, and `bom`, tend to be in high demand. If you hardcode your placement into one of those and cross your fingers, you might find yourself scaling to zero. -### How to check available capacity +### Where can you deploy? -Run `fly platform regions`. You’ll get a list of regions and their available CPU cores. These aren’t guarantees, but they’re a decent snapshot of where you’re most likely to succeed. +Run `fly platform regions` to see the regions where Fly.io has datacenters, along with their region codes. Use those codes to set region preferences for your Machines. ### Let the scheduler help