Instance locations

When you create a Cloud SQL instance, you choose a region where the instance and its data are stored. To reduce latency and increase availability, choose the same region for your data and your Compute Engine instances, App Engine apps, and other services.

There are different location types:

A regional location is a specific geographic place, such as London.

A multi-regional location is a large geographic area, such as the United States, that contains at least two geographic places. Multi- regional locations are only used for backups.

Regional Locations

Regional locations are specific geographic locations within a multi-region location. You can create a Cloud SQL instance in the following regions:

Region Name Region Description
North America
northamerica-northeast1 Montréal
us-central1 Iowa
us-east1 South Carolina
us-east4 Northern Virginia
us-west1 Oregon
us-west2 Los Angeles
South America
southamerica-east1 São Paulo
europe-north1 Finland
europe-west1 Belgium
europe-west2 London
europe-west3 Frankfurt
europe-west4 Netherlands
europe-west6 Zürich
asia-east1 Taiwan
asia-east2 Hong Kong
asia-northeast1 Tokyo
asia-northeast2 Osaka
asia-south1 Mumbai
asia-southeast1 Singapore
australia-southeast1 Sydney

Multi-regional backup locations

Multi-Region Name Multi-Region Description
asia Data centers in Asia
eu Data centers in the European Union
us Data centers in the United States


Zones are sub-locations within a region. For example, a zone named us-central1-a indicates a zone within the us-central1 region. A zone is independent of other zones in the same region.

You can choose your zone to keep your Cloud SQL instance close to your other Google Cloud Platform services. For highly-available instances (regional instances), you can choose your primary zone, but not your secondary zone.

For more information about zones, see Geography and Regions.

What's next

Was this page helpful? Let us know how we did:

Send feedback about...

Cloud SQL for PostgreSQL