Vercel Sandbox routing is now 18x faster globally
Vercel cut median Sandbox domain lookup latency from 62 ms to 3.4 ms by resolving domains from regional replicas. Agent sandboxes get the change automatically with no pricing change.
Vercel now resolves Sandbox public domains from the nearest regional replica rather than one centralized store. **Median lookup latency fell from 62 ms to 3.4 ms**, an **18× reduction**.
Builders running browser previews, callbacks, or agent-generated services on Sandbox domains get lower routing overhead automatically. No SDK migration or configuration change is described.
Vercel now resolves Sandbox public domains from the nearest regional replica rather than one centralized store. **Median lookup latency fell from 62 ms to 3.4 ms**, an **18× reduction**. Builders running browser previews, callbacks, or agent-generated services on Sandbox domains get lower routing overhead automatically. No SDK migration or configuration change is described. The largest reported gains are regional p99 figures—up to **112× in Sydney** and **146× in Cape Town**—so they should not be read as typical global latency. Process startup and application latency are outside this measurement.
This removes a specific infrastructure tax for public Sandbox endpoints by distributing domain resolution, benefiting previews, callbacks, and agent-hosted services without a described migration. It complements sandbox capability and isolation improvements, but the measurement is only routing lookup latency; it neither demonstrates faster process startup nor establishes lower end-to-end application latency.