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, standard environment 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.

You choose a location when you first create the instance. The location can't be changed after the instance is created.

Regional Locations

Regional locations are specific geographic locations within a multi-region location. Cloud SQL is currently available in all Google Cloud regions and will be offered in upcoming regional launches at the time of launch. You can create a Cloud SQL instance in the following regions:

Region Name Region Description
North America
northamerica-northeast1 Montréal
northamerica-northeast2 Toronto
us-central1 Iowa
us-east1 South Carolina
us-east4 Northern Virginia
us-west1 Oregon
us-west2 Los Angeles
us-west3 Salt Lake City
us-west4 Las Vegas
South America
southamerica-east1 São Paulo leaf icon Low CO2
europe-north1 Finland leaf icon Low CO2
europe-central2 Warsaw
europe-west1 Belgium leaf icon Low CO2
europe-west2 London
europe-west3 Frankfurt
europe-west4 Netherlands
europe-west6 Zürich leaf icon Low CO2
asia-east1 Taiwan
asia-east2 Hong Kong
asia-northeast1 Tokyo
asia-northeast2 Osaka
asia-northeast3 Seoul
asia-south1 Mumbai
asia-south2 Delhi
asia-southeast1 Singapore
asia-southeast2 Jakarta
australia-southeast1 Sydney
australia-southeast2 Melbourne

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 in a region where you can create zonal resources such as MySQL instances. 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.

For MySQL instances, you can choose your zone, and you can choose whether your data is replicated between zones or not. If you want your MySQL instance to be replicated between zones, configure it for high availability.

You can add the zone when you first create the instance. You can edit at a later time to modify the zone.

Preferred Location

For MySQL instances, you can select your zone. Choose Any if you want the system to select and assign a zone for you during instance creation.

For more information about zones, see Geography and Regions.

What's next