Vercel Edge Network Regions
View the list of regions supported by Vercel's Edge Network and learn about our global infrastructure.Vercel's 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 Content Delivery Network (CDN) and a globally distributed platform for running compute. This page outlines the regions Vercel's Edge Network supports and explains our global infrastructure.
Vercel's Edge Network is built on a sophisticated global infrastructure designed to optimize performance and reliability:
- Points of Presence (PoPs): We operate over 100 PoPs distributed across the globe. These PoPs serve as the first point of contact for incoming requests, ensuring low-latency access for users worldwide.
- Edge Regions: Behind these PoPs, we maintain 18 compute-capable regions where your code can run close to your data.
- Private Network: Traffic flows from PoPs to the nearest Edge region through private, low-latency connections, ensuring fast and efficient data transfer.
This architecture balances the benefits of widespread geographical distribution with the efficiency of concentrated caching and compute resources.
Our approach to caching is designed to maximize efficiency and performance:
- By maintaining fewer, dense regions, we increase cache hit probability. This means that popular content is more likely to be available in each region's cache.
- The extensive PoP network ensures that users can quickly access regional caches, minimizing latency.
- This concentrated caching strategy results in higher cache hit ratios, reducing the need for requests to go back to the origin server and significantly improving response times.
Region Code | Region Name | Reference Location |
|---|---|---|
| arn1 | eu-north-1 | Stockholm, Sweden |
| bom1 | ap-south-1 | Mumbai, India |
| cdg1 | eu-west-3 | Paris, France |
| cle1 | us-east-2 | Cleveland, USA |
| cpt1 | af-south-1 | Cape Town, South Africa |
| dub1 | eu-west-1 | Dublin, Ireland |
| fra1 | eu-central-1 | Frankfurt, Germany |
| gru1 | sa-east-1 | São Paulo, Brazil |
| hkg1 | ap-east-1 | Hong Kong |
| hnd1 | ap-northeast-1 | Tokyo, Japan |
| iad1 | us-east-1 | Washington, D.C., USA |
| icn1 | ap-northeast-2 | Seoul, South Korea |
| kix1 | ap-northeast-3 | Osaka, Japan |
| lhr1 | eu-west-2 | London, United Kingdom |
| pdx1 | us-west-2 | Portland, USA |
| sfo1 | us-west-1 | San Francisco, USA |
| sin1 | ap-southeast-1 | Singapore |
| syd1 | ap-southeast-2 | Sydney, Australia |
In addition to our 18 compute-capable regions, Vercel's Edge Network includes over 100 PoPs distributed across the globe. These PoPs serve several crucial functions:
- Request routing: PoPs intelligently route requests to the nearest or most appropriate edge region with single-digit millisecond latency.
- DDoS protection: They provide a first line of defense against distributed denial-of-service attacks.
- SSL termination: PoPs handle SSL/TLS encryption and decryption, offloading this work from origin servers.
The extensive PoP network ensures that users worldwide can access your content with minimal latency, even if compute resources are concentrated in fewer regions.
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.
| Region Code | Reference Location |
|---|---|
| dev1 | localhost |
- 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.
Vercel's Edge Network is designed with high availability and fault tolerance in mind:
- In the event of regional downtime, application traffic is automatically rerouted to the next closest Edge Network region. This ensures that your application remains available to users even during localized outages.
- Traffic will be rerouted to the next closest region in the following order:
Regions by priority
- For Enterprise customers, Serverless Functions can automatically failover to a different region if the region they are running in becomes unavailable. Learn more about Serverless Function failover.
This multi-layered approach to resiliency, combining our extensive PoP network with intelligent routing and regional failover capabilities, ensures high availability and consistent performance for your applications.
Was this helpful?