A typical server configuration might begin by selecting the region where the physical server is located. A local business would have no issue selecting the closest region to their store, but businesses with traffic spanning cities, countries, or even the entire globe might struggle to serve all their customers. This is where the Vercel Edge Network comes in.

Outage Resiliency

If an Edge Region goes down, an application's traffic gets rerouted to another Edge Region. If an Origin Region goes down, anything deployed to that Region automatically gets redeployed in a healthy Region.

To further increase our coverage and resiliency, we plan to utilize more cloud providers in the future and continue expanding our Regions.

Routing

The Vercel Platform acts as a Universal API and Overlay Network on top of existing cloud infrastructure providers.

Region ID
Reference Location
Provider Region
arn1
Stockholm, Sweden
AWS eu-north-1
bom1
Mumbai, India
AWS ap-south-1
cdg1
Paris, France
AWS eu-west-3
cle1
Cleveland, USA
AWS us-east-2
dub1
Dublin, Ireland
AWS eu-west-1
gru1
São Paulo, Brazil
AWS sa-east-1
hkg1
Hong Kong
AWS ap-east-1
hnd1
Tokyo, Japan
AWS ap-northeast-1
iad1
Washington, D.C., USA
AWS us-east-1
icn1
Seoul, South Korea
AWS ap-northeast-2
lhr1
London, United Kingdom
AWS eu-west-2
pdx1
Portland, USA
AWS us-west-2
sfo1
San Francisco, USA
AWS us-west-1
sin1
Singapore
AWS ap-southeast-1
syd1
Sydney, Australia
AWS ap-southeast-2

During development via vercel dev, the region is assigned dev1 to mimic the Vercel Platform infrastructure.

Region ID
Reference Location
dev1
localhost

Last Edited on June 25th 2021