# Vercel Sandbox expands from four regions to all 20 — with ordered failover Vercel Sandbox can now execute in every Vercel compute region, while Pro and Enterprise teams can define ordered failover regions and keep both primary and fallback execution inside approved geographies. For agent and untrusted-code workloads, the useful change is not simply lower latency. Sandbox location becomes an explicit execution policy, so teams can align code execution with nearby data and avoid a resilience fallback quietly moving work outside an allowed region. - Status: Active - Published: 2026-09-11T22:02:20+12:00 - Updated: 2026-09-11T22:02:20+12:00 - Categories: Artificial Intelligence, Web Development, Cloud & Infrastructure, AI Agents, Cloud Platforms, Developer Tools - Tags: AI agents, data residency, sandboxing, Vercel - Canonical HTML: https://beyondthe.news/dossiers/vercel-sandbox-all-regions-failover-data-residency ## 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. ## Key details - Vercel Sandbox now runs in all 20 Vercel compute regions, up from four. - Region selection is available on every plan. - `iad1` remains the default region. - Pro and Enterprise plans can configure ordered failover regions. - Failover regions can be restricted to approved geographies for residency requirements. - The change applies to Vercel Sandbox execution, which is commonly used for code and agent workloads. ## Builder takeaways - Set the sandbox region explicitly when execution location matters; do not assume the nearest or compliant region will be chosen automatically. - Keep failover lists inside the same approved legal/data boundary when residency is contractual. - Benchmark tool-heavy agents with the sandbox near their database and storage because repeated network calls can magnify cross-region latency. - Treat sandbox-region availability separately from the residency of the model API or external tools the agent calls; one compliant component does not make the whole workflow compliant. - Test regional failure behavior so an outage does not reveal dependencies that are reachable only from the primary location. ## What to watch - Whether Vercel adds per-region capacity or availability guarantees for Sandbox. - More granular networking and private-connectivity controls by region. - Regional pricing differences if sandbox usage grows. - How Vercel Sandbox integrates with OpenAI's newly announced Agents API and other managed agent harnesses. - Whether failover policies become available to lower-cost plans. ## Uncertainties - Regional sandbox placement does not by itself guarantee that models, third-party APIs or external storage used by the workload remain in the same geography. - Vercel does not claim that every region has identical capacity or cold-start behavior. - Failover is available only on Pro and Enterprise at launch. ## Sources - [Vercel Sandbox is now available in all regions](https://vercel.com/changelog/vercel-sandbox-is-now-available-in-all-regions) — Vercel · primary changelog · 2026-09-10T00:00:00+12:00. Primary source for expansion from four to 20 regions, default region, plan availability, failover ordering and residency controls.