Batch locations

Batch is available in the following regions. For more information about regions and zones, see Geography and regions.

Important: Only the following regions can be used for a job's location, which is used for storing job metadata. However, you can create the VMs that run your Batch job in any location with the Compute Engine resources by specifying the job's allowed locations for VMs. Otherwise, if you omit the allowedLocations[] field, the VMs that run a job are created in the job's location. To identify an existing job's location and the allowed locations for its VMs, view the details of a job.

Regions

The following table lists the regions in the Americas where Batch is available.

Region description	Region name	Details
Montréal	northamerica-northeast1	Low CO2
Toronto	northamerica-northeast2	Low CO2
São Paulo	southamerica-east1	Low CO2
Santiago	southamerica-west1	Low CO2
Iowa	us-central1	Low CO2
South Carolina	us-east1
Northern Virginia	us-east4
Columbus	us-east5
Dallas	us-south1	Low CO2
Oregon	us-west1	Low CO2
Los Angeles	us-west2
Salt Lake City	us-west3
Las Vegas	us-west4

The following table lists the regions in Europe and the Middle East where Batch is available.

Region description	Region name	Details
Warsaw	europe-central2
Finland	europe-north1	Low CO2
Madrid	europe-southwest1	Low CO2
Belgium	europe-west1	Low CO2
London	europe-west2	Low CO2
Frankfurt	europe-west3
Netherlands	europe-west4	Low CO2
Zürich	europe-west6	Low CO2
Milan	europe-west8
Paris	europe-west9	Low CO2
Berlin	europe-west10
Turin	europe-west12
Doha	me-central1
Dammam	me-central2
Tel Aviv	me-west1

The following table lists the regions in Asia Pacific where Batch is available.

Region description	Region name	Details
Taiwan	asia-east1
Hong Kong	asia-east2
Tokyo	asia-northeast1
Osaka	asia-northeast2
Seoul	asia-northeast3
Mumbai	asia-south1
Delhi	asia-south2
Singapore	asia-southeast1
Jakarta	asia-southeast2
Sydney	australia-southeast1
Melbourne	australia-southeast2

Recommended zones to obtain GPUs from Dynamic Workload Scheduler

When you create and run a job that uses GPUs and use calendar-mode reservations (Preview) or Flex-start VMs (Preview), which both use Dynamic Workload Scheduler, we recommend that you use the following zones. These recommended zones have dedicated capacity for Dynamic Workload Scheduler, so using them increases the likelihood that your requests for GPU machine type from Dynamic Workload Scheduler are approved.

A4 A3 Ultra A3 Mega A3 High

GPU machine series	Recommended zones for Dynamic Workload Scheduler capacity	Details
A4	asia-southeast1-b (Singapore)
	us-central1-b (Iowa)	Low CO2
	us-south1-b (Dallas)	Low CO2
A3 Ultra	asia-south1-b (Mumbai)
	asia-south2-c (Delhi)
	europe-west1-b (Belgium)	Low CO2
	europe-west4-a (Netherlands)	Low CO2
	us-central1-b (Iowa)	Low CO2
	us-east4-b (Northern Virginia)
	us-south1-b (Dallas)	Low CO2
A3 Mega	europe-west1-c (Belgium)	Low CO2
	europe-west4-b (Netherlands)	Low CO2
	europe-west4-c (Netherlands)	Low CO2
	us-central1-a (Iowa)	Low CO2
	us-central1-b (Iowa)	Low CO2
	us-central1-c (Iowa)	Low CO2
	us-east4-b (Northern Virginia)
A3 High	asia-east1-c (Taiwan)
	europe-west1-b (Belgium)	Low CO2
	us-central1-a (Iowa)	Low CO2
	us-central1-b (Iowa)	Low CO2