Google Cloud SQL Instance Locations

When you create a Google 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.

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 Notes
us-central Iowa First Generation instances only
us-central1 Iowa Second Generation instances only
us-east1 South Carolina
us-east4 Northern Virginia Second Generation instances only
us-west1 Oregon Second Generation instances only
Asia Pacific
asia-east1 Taiwan
asia-northeast1 Tokyo Second Generation instances only
australia-southeast1 Sydney Second Generation instances only
europe-west1 Belgium
europe-west2 London Second Generation instances only
europe-west3 Frankfurt Second Generation instances only


Zones are isolated locations within a region where you can create zonal resources such as Second Generation instances. For example, a zone named us-central1-a indicates a location in the central United States. A zone within a region is independent of other zones in the same region.

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

For First Generation instances, you cannot choose your zone. Data in First Generation instances is replicated across multiple zones, so a zonal failure does not affect the availability of your instance.

Preferred Location

For Second Generation instances, you can select your zone.

For First Generation instances, you can store your data close to a Compute Engine or App Engine service hosted within the same region. Choosing a preferred location will reduce latency and improve availability for that service. Note that if the service you have requested to remain close to moves to another zone, your Cloud SQL instance is moved also, which causes downtime.

What's next

Send feedback about...

Cloud SQL for MySQL