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.
Region Code | Region Name | Reference Location |
---|---|---|
arn1 | eu-north-1 | Stockholm, Sweden |
bom1 | ap-south-1 | Mumbai, India |
bru1 | eu-central-1 | Brussels, Belgium |
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 |
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 an 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: