Sandboxer regions

Which regions does Sandboxer have?

Sandboxer has two regions, both on dedicated servers that Sandboxer operates. The regions docs list them:

Sandboxer's own site notes that if you need more than two regions today, another service may fit better.

How is a region chosen if you don't pick one?

Without a region, a new sandbox goes to the region nearest you, judged from the country of your IP address. The lookup runs on Sandboxer's servers against a local database, and your address is not sent anywhere else.

• Europe (including the UK), the Middle East, Africa, and South and Southeast Asia go to eu-central
• The Americas, East Asia and Oceania go to us-east
• Anything that can't be placed goes to us-east

Each sandbox reports its region and a regionSource of requested, nearest, default or source, so you can always tell why it landed where it did.

How do you pick a region?

Pass region when you create a sandbox. The same option works in the CLI, the API, both SDKs and the MCP server's create_sandbox tool.

sbx regions                  # list regions and mark your nearest
sbx new --region us-east

curl -sS -X POST https://sandboxer.com/api/v1/sandboxes \
  -H "Authorization: Bearer $SANDBOXER_API_KEY" -H "Content-Type: application/json" \
  -d '{"region":"eu-central"}'

The SDKs take region as a create option too. The Daytona-compatible API reads target, which accepts us, eu or a region id.

Which region should you choose?

Choose the region closest to the people or services that talk to the sandbox most. Every command, file transfer, SSH session and hosted URL travels between you and the sandbox, so distance shows up as delay on each call. If your backend runs in Europe, eu-central keeps those round trips short; if it runs in North America, us-east does.

Sandboxer's machines page shows the effect. Measured from Virginia on 2026-10-28, a new default sandbox was ready in a median of 0.18 seconds in us-east and 0.32 seconds in eu-central, and the docs note that the EU figure includes the round trip from Virginia to Finland. Each region keeps a pool of booted, paused sandboxes ready, which is why most creates are this quick.

If you need data to stay in one region, name it explicitly rather than relying on IP lookup, which can change when you travel or route through a VPN.

Do forks and snapshots move between regions?

No. Copies stay in the region of the thing they were made from:

• A fork runs in its source sandbox's region
• A sandbox made from a named snapshot or share code starts in that snapshot's region
• A resume stays in the sandbox's region

Asking for a different region in any of these cases returns 400 region_mismatch. Plan your templates with this in mind: if you serve users in both regions, build a named snapshot in each one.

What errors can region requests return?

You can check regions without a key. GET /api/v1/regions returns each region's id, name, location and availability, plus the default and your nearest region.

curl -sS https://sandboxer.com/api/v1/regions