The Vercel Edge Network enables you to store content close to your customers and run compute in regions close to your data, reducing latency and improving end-user performance.
An Edge Network is both a CDN (Content Delivery Network) and a globally distributed platform for running compute at the edge. This page outlines the regions Vercel's Edge Network supports.
When you use Edge Functions and Edge Middleware, your code is executed in the region nearest to each user that visits your route. The same is true for Serverless Functions if you have deployed them in multiple regions.
Learn how to configure:
|cpt1||af-south-1||Cape Town, South Africa|
|gru1||sa-east-1||São Paulo, Brazil|
|iad1||us-east-1||Washington, D.C., USA|
|icn1||ap-northeast-2||Seoul, South Korea|
|lhr1||eu-west-2||London, United Kingdom|
|sfo1||us-west-1||San Francisco, USA|
In front of these 18 compute-capable regions, Vercel has over 100 points of presence (POPs) distributed across the globe. Traffic to Vercel is first routed to these POPs, and then will transit from the POPs to the nearest Edge Network region on private, low-latency, and high-bandwidth connections. This means traffic gets to and from the Vercel Edge Network as quickly and efficiently as possible.
Maintaining a smaller number of regions increases the cache hit probability as caches in each region are more likely to hold popular or frequently requested content. Combining this with a higher number of POPs results in a concentrated and efficient caching infrastructure.
When you use the
vercel dev CLI command to mimic your deployment environment locally, the region is assigned
dev1 to mimic the Vercel platform infrastructure.
- Serverless Functions default to running in the
iad1(Washington, D.C., USA) region. Learn more about changing function regions
- Edge Functions execute in the region nearest to visitors by default. Learn more about setting a specific Edge Function region
Functions should be executed in the same region as your database, or as close to it as possible, for the lowest latency.
In the event of regional downtime, application traffic is rerouted to the next closest Edge Network region. This ensures that your application is always available to your users.
Traffic will be rerouted to the next closest region in the following order: