Bucket locations

Stay organized with collections Save and categorize content based on your preferences.

This page explains the concept of bucket location and the different locations where you can create buckets. A bucket's location defines the physical place where object data in the bucket resides.

To learn how to set the location for your bucket, see Create storage buckets.

Key concepts

  • You permanently set a geographic location for storing your object data when you create a bucket.

  • You can select from the following location types:

    • A region is a specific geographic place, such as São Paulo.

    • A dual-region is a specific pair of regions, such as Tokyo and Osaka.

    • A multi-region is a large geographic area, such as the United States, that contains two or more geographic places.

  • All Cloud Storage data is redundant across at least two zones within at least one geographic place as soon as you upload it.

  • Additionally, objects stored in a multi-region or dual-region are geo-redundant. Objects that are geo-redundant are stored redundantly in at least two separate geographic places separated by at least 100 miles.

    • Default replication is designed to provide geo-redundancy for 99.9% of newly written objects within a target of one hour. Newly written objects include uploads, rewrites, copies, and compositions.

    • Turbo replication provides geo-redundancy for all newly written objects within a target of 15 minutes. Applicable only for dual-region buckets.

  • Cloud Storage stores object data in the selected location in accordance with the Service Specific Terms.

Location considerations

When you choose the location for a Cloud Storage bucket, consider the differences in availability, price, and performance, as shown in the following table.

Regional Dual-region Multi-region
Availability1
  • Data redundancy across availability zones (synchronous)
  • RTO=0: automated failover and failback on zonal failure (no need to change storage paths)
  • Higher availability than regional
  • Data redundancy across regions (asynchronous)
  • Turbo replication option for replication within 15 minutes
  • RTO=0: automated failover and failback on regional failure (no need to change storage paths)
  • Higher availability than regional
  • Data redundancy across regions (asynchronous)
  • RTO=0: automated failover and failback on regional failure (no need to change storage paths)
Performance
  • 200 Gbps (per region, per project)
  • Scalable to many Tbps by requesting higher bandwidth quota
  • 200 Gbps (per region, per project)
  • Scalable to many Tbps by requesting higher bandwidth quota
  • 50 Gbps (per region, per project)
  • Limited performance scaling, variable performance for reads
Pricing
  • Lowest storage price
  • No replication charges
  • No egress charges when reading data inside the same region
  • Highest storage price
  • Replication charges apply on write
  • No egress charges when reading data within either region
  • Higher storage price than regional, but lower than dual-region
  • Replication charges apply on write
  • Egress charges always apply when reading data
  1. The service level objective (SLO) for each location option depends on the storage class of the bucket. See the Cloud Storage Service Level Agreement (SLA).

Location recommendations

Requirements Recommended bucket location Workload examples
  • Optimized latency and bandwidth
  • Lowest data storage cost
  • Cross-zone redundancy
Regional
  • Analytics
  • Backup and archive
  • Optimized latency and bandwidth
  • Cross-region redundancy
Dual-region1
  • Analytics
  • Backup and archive
  • Disaster recovery
  • Cross-geography data access
  • Highest availability
Multi-region
  • Content serving
  1. If you need a short and predictable recovery point objective (RPO), enable the premium turbo replication feature.
  • To maximize performance and lower your total cost of ownership, co-locate your data and compute in the same region(s). Regional and dual-region locations are both suitable for this purpose.
  • To avoid data replication charges, store short-lived datasets in regional locations.
  • For moderate performance and ad hoc analytics workloads, multi-region storage can be a cost-effective choice.
  • When transferring to a new bucket, consider if the current storage class still suits your needs.

  • See the data storage pricing table for storage costs in each location.

Compute Engine VM notes

  • Storing data in the same region as your Compute Engine VM instances can provide better performance. This advantage applies to both regions and dual-regions.
  • While you can't specify a Compute Engine zone as a bucket location, all Compute Engine VM instances in zones within a given region have similar performance when accessing buckets in that region.

Available locations

The following sections list the Cloud Storage locations available for storing your data.

Regions

All regions are at least 100 miles apart.

Continent Region Name Region Description
North America
NORTHAMERICA-NORTHEAST1 Montréal leaf icon Low CO2
NORTHAMERICA-NORTHEAST2 Toronto leaf icon Low CO2
US-CENTRAL1 Iowa leaf icon Low CO2
US-EAST1 South Carolina
US-EAST4 Northern Virginia
US-EAST5 Columbus
US-SOUTH1 Dallas
US-WEST1 Oregon leaf icon Low CO2
US-WEST2 Los Angeles
US-WEST3 Salt Lake City
US-WEST4 Las Vegas
South America
SOUTHAMERICA-EAST1 São Paulo leaf icon Low CO2
SOUTHAMERICA-WEST1 Santiago
Europe
EUROPE-CENTRAL2 Warsaw
EUROPE-NORTH1 Finland leaf icon Low CO2
EUROPE-SOUTHWEST1 Madrid leaf icon Low CO2
EUROPE-WEST1 Belgium leaf icon Low CO2
EUROPE-WEST2 London
EUROPE-WEST3 Frankfurt
EUROPE-WEST4 Netherlands
EUROPE-WEST6 Zürich leaf icon Low CO2
EUROPE-WEST8 Milan
EUROPE-WEST9 Paris leaf icon Low CO2
Asia
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
Indonesia
ASIA-SOUTHEAST2 Jakarta
Middle East
ME-WEST1 Tel Aviv
Australia
AUSTRALIA-SOUTHEAST1 Sydney
AUSTRALIA-SOUTHEAST2 Melbourne

Dual-regions

The following regions are currently supported:

Continent Region Name Region Description
North America
US-CENTRAL1 Iowa
US-EAST1 South Carolina
US-EAST4 Northern Virginia
US-WEST1 Oregon
Asia
ASIA-EAST1 Taiwan
ASIA-SOUTHEAST1 Singapore
Europe
EUROPE-NORTH1 Finland
EUROPE-WEST1 Belgium
EUROPE-WEST4 Netherlands

Predefined dual-regions

The following predefined dual-regions are also supported. For more information, see Create a dual-region bucket.

Dual-Region Name Dual-Region Description
NAM4 Iowa and South Carolina
ASIA1 Tokyo and Osaka
EUR4 Finland and Netherlands

Multi-regions

Multi-Region Name Multi-Region Description
ASIA Data centers in Asia
EU Data centers within member states of the European Union*
US Data centers in the United States

* Object data added to a bucket in the EU multi-region is not stored in the EUROPE-WEST2 (London) or EUROPE-WEST6 (Zurich) regions.

What's next

Try it for yourself

If you're new to Google Cloud, create an account to evaluate how Cloud Storage performs in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

Try Cloud Storage free