NOTE: these docs are deprecated. Please see our new Subhosting docs site here instead.
Endpoints and Regions
Deno Deploy Subhosting is available in many global datacenters in both AWS and GCP. This allows you to choose which region is best for your traffic. Closer regions can reduce latency and costs. Choosing a multi-region or global region may have higher SLOs compared to single regions.
This page lists out every datacenter that Deno Deploy Subhosting is available in, and the endpoints that can be used to direct traffic to one or multiple of these regions.
Regions
AWS
| ID | Region | Location |
|---|---|---|
aws-us-east-1 |
us-east-1 |
US East (N. Virginia) |
aws-us-east-2 |
us-east-2 |
US East (Ohio) |
aws-us-west-1 |
us-west-1 |
US West (N. California) |
aws-ca-central-1 |
ca-central-1 |
Canada (Central) |
aws-eu-west-1 |
eu-west-1 |
EU (Ireland) |
aws-eu-west-2 |
eu-west-2 |
EU (London) |
aws-eu-central-1 |
eu-central-1 |
EU (Frankfurt) |
aws-ap-south-1 |
ap-south-1 |
Asia Pacific (Mumbai) |
aws-ap-southeast-1 |
ap-southeast-1 |
Asia Pacific (Singapore) |
aws-ap-southeast-2 |
ap-southeast-2 |
Asia Pacific (Sydney) |
aws-ap-northeast-1 |
ap-northeast-1 |
Asia Pacific (Tokyo) |
aws-ap-northeast-2 |
ap-northeast-2 |
Asia Pacific (Seoul) |
aws-sa-east-1 |
sa-east-1 |
South America (SĂŁo Paulo) |
aws-me-south-1 |
me-south-1 |
Middle East (Bahrain) |
aws-af-south-1 |
af-south-1 |
Africa (Cape Town) |
GCP
| ID | Region | Location |
|---|---|---|
gcp-asia-east1 |
asia-east1 |
Changhua County, Taiwan, APAC |
gcp-asia-east2 |
asia-east2 |
Hong Kong, APAC |
gcp-asia-northeast1 |
asia-northeast1 |
Tokyo, Japan, APAC |
gcp-asia-northeast2 |
asia-northeast2 |
Osaka, Japan, APAC |
gcp-asia-northeast3 |
asia-northeast3 |
Seoul, South Korea, APAC |
gcp-asia-south1 |
asia-south1 |
Mumbai, India, APAC |
gcp-asia-south2 |
asia-south2 |
Delhi, India, APAC |
gcp-asia-southeast1 |
asia-southeast1 |
Jurong West, Singapore, APAC |
gcp-asia-southeast2 |
asia-southeast2 |
Jakarta, Indonesia, APAC |
gcp-australia-southeast1 |
australia-southeast1 |
Sydney, Australia, APAC |
gcp-australia-southeast2 |
australia-southeast2 |
Melbourne, Australia, APAC |
gcp-europe-central2 |
europe-central2 |
Warsaw, Poland, Europe |
gcp-europe-north1 |
europe-north1 |
Hamina, Finland, Europe |
gcp-europe-southwest1 |
europe-southwest1 |
Madrid, Spain, Europe |
gcp-europe-west1 |
europe-west1 |
St. Ghislain, Belgium, Europe |
gcp-europe-west2 |
europe-west2 |
London, England, Europe |
gcp-europe-west3 |
europe-west3 |
Frankfurt, Germany, Europe |
gcp-europe-west4 |
europe-west4 |
Eemshaven, Netherlands, Europe |
gcp-europe-west6 |
europe-west6 |
ZĂĽrich, Switzerland, Europe |
gcp-europe-west8 |
europe-west8 |
Milan, Italy, Europe |
gcp-europe-west9 |
europe-west9 |
Paris, France, Europe |
gcp-me-west1 |
me-west1 |
Tel Aviv, Israel, Middle East |
gcp-northamerica-northeast1 |
northamerica-northeast1 |
Montréal, Canada, North America |
gcp-northamerica-northeast2 |
northamerica-northeast2 |
Toronto, Canada, North America |
gcp-southamerica-east1 |
southamerica-east1 |
Osasco, SĂŁo Paulo, Brazil, South America |
gcp-southamerica-west1 |
southamerica-west1 |
Santiago, Chile, South America |
gcp-us-central1 |
us-central1 |
Council Bluffs, Iowa, North America |
gcp-us-east1 |
us-east1 |
Moncks Corner, South Carolina, North America |
gcp-us-east4 |
us-east4 |
Ashburn, Northern Virginia, North America |
gcp-us-east5 |
us-east5 |
Columbus, Ohio, North America |
gcp-us-south1 |
us-south1 |
Dallas, Texas, North America |
gcp-us-west1 |
us-west1 |
The Dalles, Oregon, North America |
gcp-us-west2 |
us-west2 |
Los Angeles, California, North America |
gcp-us-west3 |
us-west3 |
Salt Lake City, Utah, North America |
gcp-us-west4 |
us-west4 |
Las Vegas, Nevada, North America |
Endpoints
Single region
These endpoints direct traffic at a specific single region. If this region is unavailable, traffic will be dropped.
| ID | Endpoint URL |
|---|---|
aws-us-east-1 |
https://us-east-1.subhosting-v1.deno-aws.net |
aws-us-east-2 |
https://us-east-2.subhosting-v1.deno-aws.net |
aws-us-west-1 |
https://us-west-1.subhosting-v1.deno-aws.net |
aws-ca-central-1 |
https://ca-central-1.subhosting-v1.deno-aws.net |
aws-eu-west-1 |
https://eu-west-1.subhosting-v1.deno-aws.net |
aws-eu-west-2 |
https://eu-west-2.subhosting-v1.deno-aws.net |
aws-eu-central-1 |
https://eu-central-1.subhosting-v1.deno-aws.net |
aws-ap-south-1 |
https://ap-south-1.subhosting-v1.deno-aws.net |
aws-ap-southeast-1 |
https://ap-southeast-1.subhosting-v1.deno-aws.net |
aws-ap-southeast-2 |
https://ap-southeast-2.subhosting-v1.deno-aws.net |
aws-ap-northeast-1 |
https://ap-northeast-1.subhosting-v1.deno-aws.net |
aws-ap-northeast-2 |
https://ap-northeast-2.subhosting-v1.deno-aws.net |
aws-sa-east-1 |
https://sa-east-1.subhosting-v1.deno-aws.net |
aws-me-south-1 |
https://me-south-1.subhosting-v1.deno-aws.net |
aws-af-south-1 |
https://af-south-1.subhosting-v1.deno-aws.net |
gcp-asia-east1 |
https://asia-east1.subhosting-v1.deno-gcp.net |
gcp-asia-east2 |
https://asia-east2.subhosting-v1.deno-gcp.net |
gcp-asia-northeast1 |
https://asia-northeast1.subhosting-v1.deno-gcp.net |
gcp-asia-northeast2 |
https://asia-northeast2.subhosting-v1.deno-gcp.net |
gcp-asia-northeast3 |
https://asia-northeast3.subhosting-v1.deno-gcp.net |
gcp-asia-south1 |
https://asia-south1.subhosting-v1.deno-gcp.net |
gcp-asia-south2 |
https://asia-south2.subhosting-v1.deno-gcp.net |
gcp-asia-southeast1 |
https://asia-southeast1.subhosting-v1.deno-gcp.net |
gcp-asia-southeast2 |
https://asia-southeast2.subhosting-v1.deno-gcp.net |
gcp-australia-southeast1 |
https://australia-southeast1.subhosting-v1.deno-gcp.net |
gcp-australia-southeast2 |
https://australia-southeast2.subhosting-v1.deno-gcp.net |
gcp-europe-central2 |
https://europe-central2.subhosting-v1.deno-gcp.net |
gcp-europe-north1 |
https://europe-north1.subhosting-v1.deno-gcp.net |
gcp-europe-southwest1 |
https://europe-southwest1.subhosting-v1.deno-gcp.net |
gcp-europe-west1 |
https://europe-west1.subhosting-v1.deno-gcp.net |
gcp-europe-west2 |
https://europe-west2.subhosting-v1.deno-gcp.net |
gcp-europe-west3 |
https://europe-west3.subhosting-v1.deno-gcp.net |
gcp-europe-west4 |
https://europe-west4.subhosting-v1.deno-gcp.net |
gcp-europe-west6 |
https://europe-west6.subhosting-v1.deno-gcp.net |
gcp-europe-west8 |
https://europe-west8.subhosting-v1.deno-gcp.net |
gcp-europe-west9 |
https://europe-west9.subhosting-v1.deno-gcp.net |
gcp-me-west1 |
https://me-west1.subhosting-v1.deno-gcp.net |
gcp-northamerica-northeast1 |
https://northamerica-northeast1.subhosting-v1.deno-gcp.net |
gcp-nothamerica-northeast2 |
https://northamerica-northeast2.subhosting-v1.deno-gcp.net |
gcp-southamerica-east1 |
https://southamerica-east1.subhosting-v1.deno-gcp.net |
gcp-southamerica-east2 |
https://southamerica-east2.subhosting-v1.deno-gcp.net |
gcp-us-central1 |
https://us-central1.subhosting-v1.deno-gcp.net |
gcp-us-east1 |
https://us-east1.subhosting-v1.deno-gcp.net |
gcp-us-east4 |
https://us-east4.subhosting-v1.deno-gcp.net |
gcp-us-east5 |
https://us-east5.subhosting-v1.deno-gcp.net |
gcp-us-south1 |
https://us-south1.subhosting-v1.deno-gcp.net |
gcp-us-west1 |
https://us-west1.subhosting-v1.deno-gcp.net |
gcp-us-west2 |
https://us-west2.subhosting-v1.deno-gcp.net |
gcp-us-west3 |
https://us-west3.subhosting-v1.deno-gcp.net |
gcp-us-west4 |
https://us-west4.subhosting-v1.deno-gcp.net |
Multi-region
Multi-regions are a grouping of three single regions. Requests sent to a multi-region will be routed to the closest single region, based on latency, but may fall back to another single region if the closest single region is unavailable.
Multi-regions are grouped by latency. Every single region has a multi-region
that provides the best possible combination of latency and availability. This is
called the “primary” multi-region for the single region. For example,
aws-us-east-1’s primary multi-region is aws-na-1, even though it is part of
both the aws-na-1, aws-na-2, and aws-sa-1 multi-regions.
Multi-regions are only available on AWS.
| ID | Consituent Single Regions |
|---|---|
aws-na-1 |
aws-us-east-1, aws-us-east-2, aws-ca-central-1 |
aws-na-2 |
aws-us-west-1, aws-us-east-2, aws-us-east-1 |
aws-eu-1 |
aws-eu-central-1, aws-eu-west-1, aws-eu-west-2 |
aws-ap-1 |
aws-ap-south-1, aws-me-south-1, aws-ap-southeast-1 |
aws-ap-2 |
aws-ap-southeast-1, aws-ap-south-1, aws-ap-northeast-2 |
aws-ap-3 |
aws-ap-southeast-2, aws-ap-southeast-1, aws-ap-northeast-1 |
aws-ap-4 |
aws-ap-northeast-1, aws-ap-northeast-2, aws-ap-southeast-1 |
aws-sa-1 |
aws-sa-east-1, aws-us-east-1, aws-us-east-2 |
aws-me-1 |
aws-me-south-1, aws-ap-south-1, aws-eu-central-1 |
aws-af-1 |
aws-af-south-1, aws-eu-west-2, aws-eu-central-1 |
| ID | Endpoint URL |
|---|---|
aws-na-1 |
https://na-1.subhosting-v1.deno-aws.net |
aws-na-2 |
https://na-2.subhosting-v1.deno-aws.net |
aws-eu-1 |
https://eu-1.subhosting-v1.deno-aws.net |
aws-ap-1 |
https://ap-1.subhosting-v1.deno-aws.net |
aws-ap-2 |
https://ap-2.subhosting-v1.deno-aws.net |
aws-ap-3 |
https://ap-3.subhosting-v1.deno-aws.net |
aws-ap-4 |
https://ap-4.subhosting-v1.deno-aws.net |
aws-sa-1 |
https://sa-1.subhosting-v1.deno-aws.net |
aws-me-1 |
https://me-1.subhosting-v1.deno-aws.net |
aws-af-1 |
https://af-1.subhosting-v1.deno-aws.net |
| Single region | Primary multi-region | Max failover latency |
|---|---|---|
aws-us-east-1 |
aws-na-1 |
16ms |
aws-us-east-2 |
aws-na-1 |
25ms |
aws-us-west-1 |
aws-na-2 |
62ms |
aws-ca-central-1 |
aws-na-1 |
25ms |
aws-eu-central-1 |
aws-eu-1 |
29ms |
aws-eu-west-1 |
aws-eu-1 |
29ms |
aws-eu-west-2 |
aws-eu-1 |
18ms |
aws-ap-south-1 |
aws-ap-1 |
60ms |
aws-ap-southeast-1 |
aws-ap-2 |
73ms |
aws-ap-southeast-2 |
aws-ap-3 |
108ms |
aws-ap-northeast-1 |
aws-ap-4 |
74ms |
aws-ap-northeast-2 |
aws-ap-2 |
71ms |
aws-sa-east-1 |
aws-sa-1 |
125ms |
aws-me-south-1 |
aws-me-1 |
85ms |
aws-af-south-1 |
aws-af-1 |
156ms |
The max failover latency is the maximum amount of time that a request may additionally travel through networks (on average) if the primary single region is unavailable. For example, if the primary single region for
aws-na-1isaws-us-east-1, andaws-us-east-1is unavailable, the request may be routed toaws-us-east-2oraws-ca-central-1. The max failover latency is the maximum latency betweenaws-us-east-1and either ofaws-us-east-2oraws-ca-central-1(in this case 24ms).
Global
The global region is a grouping of all single regions within a provider. Requests sent to the global region will be routed to the closest single region, based on latency, but may fall back to another single region if the closest single region is unavailable.
| ID | Endpoint URL |
|---|---|
aws-global |
https://subhosting-v1.deno-aws.net |
gcp-global |
https://subhosting-v1.deno-gcp.net |