What changed
Vercel expanded Sandbox from four compute regions to all 20 on September 10, 2026. Developers can select a region on every plan, with `iad1` remaining the default. Pro and Enterprise customers can also configure an ordered list of failover regions: if a sandbox cannot be created in the primary region, Vercel tries the configured alternatives in sequence. Both primary and fallback regions can be limited to approved geographies for data-residency or regional-processing requirements.
Why it matters
Agent sandboxes often sit next to databases, storage and private services, so their execution location affects latency, data movement and compliance boundaries. Expanding to the full Vercel footprint makes regional sandbox placement practical rather than exceptional. The ordered failover control matters even more: availability policy no longer has to mean 'run somewhere else.' Teams can define resilience while keeping execution inside jurisdictions they are allowed to use.
All 20 Vercel compute regions can now host sandboxes
The service moves from four supported regions to Vercel's full compute footprint. Region selection is available on every plan, which makes location a normal part of sandbox creation rather than an enterprise-only feature.
Failover is explicit and ordered
Pro and Enterprise teams can list fallback regions. Vercel tries them in order when the primary region cannot create a sandbox, giving teams a deterministic regional recovery path instead of an opaque global fallback.
Residency constraints can include the failure path
Teams with geography requirements can restrict both primary and failover choices to approved regions. That closes an easy compliance gap where the happy path runs locally but an outage silently moves code or data processing elsewhere.
Regional proximity can reduce agent/tool latency
Sandboxed agents frequently call databases, object stores and APIs. Placing execution near those dependencies can reduce round trips, especially for tool-heavy workflows that make many sequential calls.
The default still matters
`iad1` remains the default. Applications with residency or latency requirements should not rely on the platform default; they need to select and test the intended region explicitly.