Skip to content
Last updated on March 10, 2023
3 min read

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.

Regions table
Region Code
Region Name
Reference Location
arn1eu-north-1Stockholm, Sweden
bom1ap-south-1Mumbai, India
bru1eu-central-1Brussels, Belgium
cdg1eu-west-3Paris, France
cle1us-east-2Cleveland, USA
cpt1af-south-1Cape Town, South Africa
dub1eu-west-1Dublin, Ireland
fra1eu-central-1Frankfurt, Germany
gru1sa-east-1São Paulo, Brazil
hkg1ap-east-1Hong Kong
hnd1ap-northeast-1Tokyo, Japan
iad1us-east-1Washington, D.C., USA
icn1ap-northeast-2Seoul, South Korea
kix1ap-northeast-3Osaka, Japan
lhr1eu-west-2London, United Kingdom
pdx1us-west-2Portland, USA
sfo1us-west-1San Francisco, USA
sin1ap-southeast-1Singapore
syd1ap-southeast-2Sydney, 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

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:

Regions by priority

P0iad1
P1cle1
P2sfo1
P3dub1
P4pdx1
P5lhr1
P6cdg1
P7fra1
P8bru1
P9arn1
P10gru1
P11hnd1
P12kix1
P13icn1
P14bom1
P15hkg1
P16syd1
P17sin1
P18cpt1