Apigee locations

This page applies to Apigeeand Apigee hybrid.

View Apigee Edge documentation.

Apigee organization resources can be created in many locations . These locations represent the geographical regions where Apigee resources, such as the Apigee runtime infrastructure and Apigee API Analytics data, are stored and accessed. Google manages these resources so that they are available redundantly in all zones within that region .

Meeting your latency, availability, or durability requirements are primary factors for selecting the region where your Apigee resources are located. You should consider the locations where Apigee is available and the locations of the other Google Cloud products and services that Apigee may use. Using services across multiple locations can affect Apigee's latency and its pricing .

Select a runtime region

You select the Apigee runtime hosting region when you provision your Apigee instance. You can select the runtime region when you provision using the Apigee UI in Cloud console or using the API. The following resources outline the steps required to select a runtime hosting region, based on your organization type:

Organization type
Provisioning method
Documentation
Evaluation organization
Apigee UI in Cloud console
Command line interface
Subscription organization
Apigee UI in Cloud console
Command line interface
Pay-as-you-go organization
Apigee UI in Cloud console
Command line interface

Available Apigee runtime regions

The following table lists available regions for the Apigee runtime.

Americas

Region description Region name Details
Iowa
us-central1 leaf icon Low CO 2

API hub supported

Oregon
us-west1 leaf icon Low CO 2

API hub supported

Los Angeles
us-west2

API hub supported

Salt Lake City
us-west3

API hub supported

Las Vegas
us-west4

API hub supported

Montréal
northamerica-northeast1 leaf icon Low CO 2

API hub supported

Toronto
northamerica-northeast2 leaf icon Low CO 2

API hub supported

Mexico
northamerica-south1
South Carolina
us-east1

API hub supported

Northern Virginia
us-east4

API hub supported

Columbus
us-east5

API hub supported

Dallas
us-south1

API hub supported

Santiago
southamerica-west1 leaf icon Low CO 2

API hub supported

São Paulo
southamerica-east1 leaf icon Low CO 2

API hub supported

Europe

Region description Region name Details
Belgium
europe-west1 leaf icon Low CO 2

API hub supported

London
europe-west2 leaf icon Low CO 2

API hub supported

Frankfurt
europe-west3

API hub supported

Netherlands
europe-west4

API hub supported

Zurich
europe-west6 leaf icon Low CO 2

API hub supported

Milan
europe-west8

API hub supported

Paris
europe-west9 leaf icon Low CO 2

API hub supported

Berlin
europe-west10

API hub supported

td>
Turin
europe-west12

API hub supported

Warsaw
europe-central2

API hub supported

Madrid
europe-southwest1 leaf icon Low CO 2

API hub supported

Finland
europe-north1 leaf icon Low CO 2

API hub supported

Stockholm
europe-north2 leaf icon Low CO 2

Asia-Pacific

Region description Region name Details
Sydney
australia-southeast1

API hub supported

Melbourne
australia-southeast2

API hub supported

Mumbai
asia-south1

API hub supported

Delhi
asia-south2

API hub supported

Singapore
asia-southeast1

API hub supported

Jakarta
asia-southeast2

API hub supported

Tokyo
asia-northeast1

API hub supported

Osaka
asia-northeast2

API hub supported

Seoul
asia-northeast3

API hub supported

Taiwan
asia-east1

API hub supported

Hong Kong
asia-east2

API hub supported

Middle East

Region description Region name Details
Doha
me-central1

API hub supported

Dammam
me-central2

API hub supported

Tel Aviv
me-west1

API hub supported

Africa

Region description Region name Details
Johannesburg
africa-south1

API hub supported

Select an Apigee API Analytics region

You select the region where your Apigee API Analytics data is stored when you provision your Apigee organization. You can select the runtime region when you provision using the Apigee UI in Cloud console or using the API. The following resources outline the steps required to select an Apigee API Analytics region, based on your organization type:

Organization type
Provisioning method
Documentation

Available Apigee API Analytics regions

The following table lists available regions for Apigee API Analytics.

Americas

Region description Region name Details
Iowa
us-central1 leaf icon Low CO 2

API hub supported

Oregon
us-west1 leaf icon Low CO 2

API hub supported

Los Angeles
us-west2

API hub supported

Salt Lake City
us-west3

API hub supported

Las Vegas
us-west4

API hub supported

Montréal
northamerica-northeast1 leaf icon Low CO 2

API hub supported

Toronto
northamerica-northeast2 leaf icon Low CO 2

API hub supported

South Carolina
us-east1

API hub supported

Northern Virginia
us-east4

API hub supported

Columbus
us-east5

API hub supported

Dallas
us-south1

API hub supported

Santiago
southamerica-west1 leaf icon Low CO 2

API hub supported

Europe

Region description Region name Details
Belgium
europe-west1 leaf icon Low CO 2
London
europe-west2 leaf icon Low CO 2

API hub supported

Frankfurt
europe-west3

API hub supported

Netherlands
europe-west4

API hub supported

Zurich
europe-west6 leaf icon Low CO 2

API hub supported

Milan
europe-west8

API hub supported

Paris
europe-west9 leaf icon Low CO 2

API hub supported

Berlin
europe-west10

API hub supported

Turin
europe-west12

API hub supported

Madrid
europe-southwest1 leaf icon Low CO 2

API hub supported

Warsaw
europe-central2

API hub supported

Finland
europe-north1 leaf icon Low CO 2

API hub supported

Asia-Pacific

Region description Region name Details
Sydney
australia-southeast1

API hub supported

Melbourne
australia-southeast2

API hub supported

Mumbai
asia-south1

API hub supported

Delhi
asia-south2

API hub supported

Singapore
asia-southeast1

API hub supported

Jakarta
asia-southeast2

API hub supported

Taiwan
asia-east1

API hub supported

Tokyo
asia-northeast1

API hub supported

Osaka
asia-northeast2

API hub supported

Seoul
asia-northeast3

API hub supported

Middle East

Region description Region name Details
Doha
me-central1

API hub supported

Dammam
me-central2

API hub supported

Tel Aviv
me-west1

API hub supported

Africa

Region description Region name Details
Johannesburg
africa-south1

API hub supported

Select an Apigee API control plane hosting jurisdiction

You select the specific Apigee control plane hosting jurisdiction where your data is stored when you provision your Apigee instance. Note that a jurisdiction refers to a location within a geopolitical boundary that may span more than one region.

You can select the control plane hosting jurisdiction when you provision using the Apigee UI in Google Cloud console, or using the API. The following resources outline the steps required to select a control plane hosting jurisdiction, based on your organization type:

Organization type
Provisioning method
Documentation
Subscription organization
Apigee UI in Cloud console
Command line interface
Pay-as-you-go organization
Apigee UI in Cloud console
Command line interface

Available Apigee API control plane hosting jurisdictions

The Apigee control plane directly binds to the API host name. apigee.googleapis.com has a global control plane; if you want to use a regionalized control plane, the API host name is CONTROL_PLANE_LOCATION -apigee.googleapis.com . See Data residency service endpoint for more information.

The following table lists available hosting jurisdictions and regions for the Apigee control plane.

Americas

Control plane hosting jurisdiction description Control plane hosting jurisdiction name Details
United States
us (multiple regions in United States) Service endpoint: us-apigee.googleapis.com
Canada
ca (multiple regions in Canada) Service endpoint: ca-apigee.googleapis.com
Consumer data region description Consumer data region name Details
Iowa
us-central1 leaf icon Low CO 2
Oregon
us-west1 leaf icon Low CO 2
Los Angeles
us-west2
Salt Lake City
us-west3
Las Vegas
us-west4
South Carolina
us-east1
Northern Virginia
us-east4
Columbus
us-east5
Dallas
us-south1
Montréal
northamerica-northeast1 leaf icon Low CO 2
Toronto
northamerica-northeast2 leaf icon Low CO 2

Europe

Control plane hosting jurisdiction description Control plane hosting jurisdiction name Details
European Union
eu (multiple regions in the European Union) Service endpoint: eu-apigee.googleapis.com
Germany
de (multiple regions in Germany) Service endpoint: de-apigee.googleapis.com
France
fr (single region europe-west9) Service endpoint: fr-apigee.googleapis.com
Switzerland
ch (single region europe-west6) Service endpoint: ch-apigee.googleapis.com
Consumer data region description Consumer data region name Details
Belgium
europe-west1 leaf icon Low CO 2
Frankfurt
europe-west3
Netherlands
europe-west4
Zurich
europe-west6 leaf icon Low CO 2
Milan
europe-west8
Paris
europe-west9 leaf icon Low CO 2
Turin
europe-west12
Warsaw
europe-central2
Madrid
europe-southwest1 leaf icon Low CO 2
Finland
europe-north1 leaf icon Low CO 2

Asia-Pacific

Control plane hosting jurisdiction description Control plane hosting jurisdiction name Details
Australia
au (multiple regions in Australia) Service endpoint: au-apigee.googleapis.com
India
in (multiple regions in India) Service endpoint: in-apigee.googleapis.com
Japan
jp (multiple regions in Japan) Service endpoint: jp-apigee.googleapis.com
Consumer data region description Consumer data region name Details
Sydney
australia-southeast1
Melbourne
australia-southeast2
Mumbai
asia-south1
Delhi
asia-south2
Tokyo
asia-northeast1
Osaka
asia-northeast2

Middle East

Control plane hosting juridiction description Control plane hosting jurisdiction name Details
Qatar
qa (single region me-central1) Service endpoint: qa-apigee.googleapis.com
Saudi Arabia
sa (single region me-central2) Service endpoint: sa-apigee.googleapis.com
Israel
il (single region me-west1) Service endpoint: il-apigee.googleapis.com
Consumer data region description Consumer data region name Details
Dammam
me-central2
Tel Aviv
me-west1
Design a Mobile Site
View Site in Mobile | Classic
Share by: