Vercel
Vercel Sandbox now routes requests to public domains 18x faster globally. Median domain lookup latency has fallen from 62ms to 3.4ms, with larger gains recorded in regions far from the previous central store.
The Vercel changelog explains that public domains created through the sandbox.domain() SDK call are now resolved using the nearest regional replica. Previously, those lookups went through one centralised store.
The change reduces the time between an incoming request reaching the public domain and reaching the process running inside the sandbox. It applies to every request made to a sandbox domain.
How Vercel Sandbox routing changed
The main change is where Vercel resolves each sandbox domain. Instead of sending every lookup to the same store, the platform can answer from a geographically closer replica.
That cuts the network distance involved in the lookup. The published 18x improvement is based on median domain lookup latency across Vercel’s global routing system.
- Median lookup latency
- 3.4ms
- down from 62ms
- Global routing improvement
- 18x
- median domain lookup latency
- Sydney improvement
- Up to 112x
- measured at p99
- Cape Town improvement
- Up to 146x
- measured at p99
The regional results show the biggest improvement at the 99th percentile, which tracks slower requests near the end of the latency distribution. Sydney, identified as syd1, recorded lookups up to 112x faster. Cape Town, or cpt1, reached up to 146x faster.
These figures cover public domain lookup latency. They do not describe an 18x increase in the execution speed of the code running inside a sandbox.
The faster routing applies automatically
Builders do not need to opt into the routing change. Vercel says it applies automatically to every sandbox domain request, including domains created through the existing sandbox.domain() call.
There is no pricing change attached to the improvement. For more context on the platform’s recent releases, see What Vercel Shipped in Early September.
Frequently asked questions
What is Vercel Sandbox routing?
Vercel Sandbox routing directs requests from a public domain created with sandbox.domain() to the process running inside the sandbox. Domain lookups are now resolved from the nearest regional replica rather than one centralised store.
How much faster is Vercel Sandbox routing?
Median domain lookup latency dropped from 62ms to 3.4ms, an 18x global improvement. At p99, lookups are up to 112x faster in Sydney and up to 146x faster in Cape Town.
Does faster Vercel Sandbox routing cost more?
No. The routing improvement applies automatically to every sandbox domain request, with no pricing changes.
Sources
3 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.
Stripe
Supabase