Skip to content

Vercel Edge Network Regions

View the list of regions supported by Vercel's Edge Network.
Table of Contents
Choose a framework to optimize documentation to:

    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:

    Regions table
    Region Code
    Region Name
    Reference Location
    arn1eu-north-1Stockholm, Sweden
    bom1ap-south-1Mumbai, India
    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

    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.

    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
    P8arn1
    P9gru1
    P10hnd1
    P11kix1
    P12icn1
    P13bom1
    P14hkg1
    P15syd1
    P16sin1
    P17cpt1
    Last updated on February 17, 2023