Vercel Sandbox is now globally available

Vercel Sandbox now runs globally, starting with four regions: iad1 (Washington, D.C.), sfo1 (San Francisco), cle1 (Cleveland), and cdg1 (Paris). iad1 remains the default. Support for all Vercel regions is coming soon. Choose a region close to the databases, object storage, and other services your sandboxes access to reduce latency. Region selection is available on all plans. Pro and Enterprise teams can also configure failover regions. If the primary region is unavailable, new sandboxes start in the closest configured failover region. Snapshots stay in the region where they were created and can't be moved. To create or resume a sandbox from a snapshot, both must be in the same region. During failover, Vercel handles this automatically by loading the snapshot across regions. Update the SDK or CLI you use to the latest version: pnpm install @vercel/sandbox@latest # Sandbox SDKpnpm install -g sandbox@latest # Sandbox CLI pnpm install -g vercel@latest # Vercel CLI Configure the default region and failover regions from Settings > Sandboxes in your project, or with the Vercel CLI: vercel project update my-project --sandbox-region cdg1 --sandbox-failover-regions iad1,cle1 Configure Sandbox defaults with the CLI. By default, the SDK uses the regions in your project settings. To override those defaults, pass region and, optionally, failoverRegions to Sandbox.create() : import { Sandbox } from "@vercel/sandbox"; const sandbox = await Sandbox.create({ region: "cdg1", failoverRegions: ["iad1", "cle1"],}); Create a Sandbox in cdg1 with iad1 as a failover region using the SDK. Or specify regions when creating a sandbox with the Sandbox CLI: sandbox create --name my-sandbox --region cdg1 --failover-regions iad1,cle1 Create a Sandbox in cdg1 with iad1 as a failover region using the CLI. Learn more in the Sandbox regions documentation.