Vercel Sandbox now runs in four regions - iad1 (Washington, D.C.), sfo1 (San Francisco), cle1 (Cleveland), and cdg1 (Paris) - with iad1 as the default and support for all Vercel regions planned. Developers can pick a region per sandbox or set a project-wide default, and Pro/Enterprise teams can configure failover regions so new sandboxes start in the closest available region if the primary is down. Snapshots remain tied to their creation region and can't be moved, though Vercel automatically loads snapshots across regions during failover. Configuration is available via project settings, the Vercel CLI, the Sandbox CLI, or the SDK's Sandbox.create() method, and users are advised to update to the latest SDK/CLI versions.
Questions this post answers
What regions does Vercel Sandbox support now?
Vercel Sandbox runs in four regions: iad1 (Washington, D.C.), sfo1 (San Francisco), cle1 (Cleveland), and cdg1 (Paris), with iad1 as the default. Support for additional Vercel regions is planned. Region selection is available on all plans, letting teams place sandboxes closer to the databases and services they access to reduce latency. daily.dev helps developers building on vercel sandbox stay current on region rollouts like this.
How do I configure failover regions for Vercel Sandbox?
Failover regions can be set via the Vercel CLI with a command like `vercel project update my-project --sandbox-region cdg1 --sandbox-failover-regions iad1,cle1`, through project Settings > Sandboxes, or per-sandbox by passing `failoverRegions` to `Sandbox.create()` in the SDK. If the primary region is unavailable, new sandboxes start in the nearest configured failover region, available only on Pro and Enterprise plans. Engineers designing resilient sandbox deployments can track infrastructure changes like this on daily.dev.
Can a Vercel Sandbox snapshot be moved to a different region?
No, snapshots stay in the region where they were created and cannot be moved manually. To create or resume a sandbox from a snapshot, both must be in the same region, though during failover Vercel automatically loads the snapshot across regions so recovery still works without manual intervention. daily.dev keeps developers relying on snapshot-based workflows informed about infrastructure constraints like this.