When you provision aCloud Firestore instance, you must choose alocation for the instance. To reduce latency and increase availability, storeyour data close to the users and services that need it.

If your project is on the pay-as-you-go Blaze pricing plan,then you can optionallycreate multiple databases in your project,each with its own location setting.

Be aware that once you provision a database instance, you cannot change itslocation setting.

Important: The location setting for yourdefaultCloud Firestore database instance has adependency on the "location of defaultGoogle Cloud resources". This means that when you provision your defaultCloud Firestore database, its location might have already been set, either during project creation or when setting up another service that shares this location dependency.

AnyRealtime Database instances and any non-defaultCloud Firestore database instances in your project do not share this location dependency.

Types of locations

You can store yourCloud Firestore data in amulti-region location or aregional location.

Multi-region locations

Select a multi-region location to maximize the availability anddurability of your database.

A multi-region location consists of a defined set ofregions where multiple replicas of the databaseare stored. Each replica is either a read-write replica which contains all of thedata in the database or a witness replica which does not maintain a full set ofdata but participates in replication.

By replicating the data between multiple regions, datacan continue to be served even with the loss of an entireregion. Within a region, data is replicated acrosszones so that data can continue to be servedwithin that region even with the loss of a zone.

Cloud Firestore supports the following multi-region locations:

Multi-region name	Multi-region description	Read-Write regions	Witness region
eur3	Europe	europe-west1 (Belgium),europe-west4 (Netherlands)	europe-north1 (Finland)
nam5	United States (Central)	us-central1 (Iowa),us-central2 (Oklahoma—private GCP region)	us-east1 (South Carolina)
nam7	United States (Central and East)	us-central1 (Iowa),us-east4 (Northern Virginia)	us-central2 (Oklahoma—privateGoogle Cloud region)

Note: If your project already has anApp Engine app with a locationof eitherus-central oreurope-west, then yourdefaultCloud Firestore database will be consideredmulti-regional.

Regional locations

A regional location is a specific geographic place, such as South Carolina. Datain a regional location is replicated in multiple zones within aregion.

Select a regional location for lower costs, for lower write latency if yourapplication is sensitive to latency, or forco-location with otherGoogle Cloud resources.

Cloud Firestore supports the following regional resource locations:

	Region name	Region description
North America
	us-west1	Oregon
	us-west2	Los Angeles
	us-west3	Salt Lake City
	us-west4	Las Vegas
	us-central1	Iowa
	northamerica-northeast1	Montréal
	northamerica-northeast2	Toronto
	northamerica-south1	Queretaro
	us-east1	South Carolina
	us-east4	Northern Virginia
	us-east5	Columbus
	us-south1	Dallas
South America
	southamerica-west1	Santiago
	southamerica-east1	São Paulo
Europe
	europe-west2	London
	europe-west1	Belgium
	europe-west4	Netherlands
	europe-west8	Milan
	europe-southwest1	Madrid
	europe-west9	Paris
	europe-west12	Turin
	europe-west10	Berlin
	europe-west3	Frankfurt
	europe-north1	Finland
	europe-north2	Stockholm
	europe-central2	Warsaw
	europe-west6	Zürich
Middle East
	me-central1	Doha
	me-central2	Dammam
	me-west1	Tel Aviv
Asia
	asia-south1	Mumbai
	asia-south2	Delhi
	asia-southeast1	Singapore
	asia-southeast2	Jakarta
	asia-east2	Hong Kong
	asia-east1	Taiwan
	asia-northeast1	Tokyo
	asia-northeast2	Osaka
	asia-northeast3	Seoul
Australia
	australia-southeast1	Sydney
	australia-southeast2	Melbourne
Africa
	africa-south1	Johannesburg

Location SLA

YourCloud Firestore location type determines theService Level Agreement (SLA)uptime percentage:

Covered service	Monthly uptime percentage
Cloud Firestore Multi-Region	>= 99.999%
Cloud Firestore Regional	>= 99.99%

Location pricing

YourCloud Firestore location determines the cost of databaseoperations.

For a comprehensive explanation of pricing per region and per region type,seeUnderstandCloud Firestore billing.

View the location of your databases

In the Firebase console, go to theCloud FirestoreData tab to view the list of your database instances and their locations.

Possible location dependencies due to "location for defaultGoogle Cloud resources"

The "location for defaultGoogle Cloud resources" is the location settingfor any project resources associated with GoogleApp Engine, including thefollowing:

• defaultCloud Firestore database instance
• defaultCloud Storage for Firebase bucket with the name format of*.appspot.com
• GoogleCloud Scheduler used specifically with 1st gen scheduled functions

Note: None of the other resources in your project share this locationdependency, including the following: Realtime Database instances,non-defaultCloud Firestore instances, non-defaultCloud Storage buckets,defaultCloud Storage buckets with the name format of*.firebasestorage.app, non-scheduled functions,and 2nd gen scheduled functions.

This "location for defaultGoogle Cloud resources" is an immutablesetting. Also, when you set the location for one of the associated resources,you indirectly set the location for all of them due to their common associationwithApp Engine.

However, with many changes to the Firebase andGoogle Cloud ecosystem overthe years, the associations of resources toApp Engine have beenchanging. Most notably, startingOctober 30, 2024, all newly provisioneddefaultCloud Storage for Firebase buckets have the name format*.firebasestorage.app, and they arenot associatedwithApp Engine.

Key Point: StartingOctober 30, 2024,provisioning the defaultCloud Storage for Firebase bucket does not set the"location for defaultGoogle Cloud resources" (like the location for theproject's defaultCloud Firestore instance). Also, provisioning thedefaultCloud Firestore instance no longer sets the location for a newdefaultCloud Storage for Firebase bucket (with name format of*.firebasestorage.app).

Here are the details of what changed in the possiblelocation dependencies:

• StartingOctober 30, 2024,if thedefaultCloud Firestore instance and thedefaultCloud Storage for Firebase bucket arenot yet provisioned:

  • Provisioning the defaultCloud Firestore instance sets the locationfor any futureApp Engine app provisioned in the project.However, it doesnot dictate the location of the futuredefaultCloud Storage bucket.

  • Provisioning the defaultCloud Storage bucketno longer provisionsanApp Engine app. Thus, the location of thedefaultCloud Storage bucket doesnot dictate the location of thefuture defaultCloud Firestore instance.

• StartingOctober 30, 2024,if the defaultCloud Firestore instance hasalready been provisioned, but thedefaultCloud Storage for Firebase bucket hasnot been provisioned:

  • The existing defaultCloud Firestore instance doesnot dictate thelocation of the future defaultCloud Storage bucket(*.firebasestorage.app).

• StartingOctober 30, 2024,if thedefaultCloud Storage for Firebase bucket hasalready beenprovisioned (specifically, the*.appspot.com bucket), but thedefaultCloud Firestore instance hasnot been provisioned:

  • Back when the defaultCloud Storage bucket(*.appspot.com) was provisioned,anApp Engine app wasalso provisioned, and thus the locationof the future defaultCloud Firestore instance was set at that time.Even if you delete the*.appspot.com bucket, youcan't delete theApp Engine app, so the location setting of thefuture defaultCloud Firestore instance is already set.

If you used1st gen scheduled functions, then their location is set to thelocation for defaultGoogle Cloud resources. This is becauseCloud Scheduler andApp Engine previously had an association witheach other. Also, if you set up 1st gen scheduled functionsbeforeprovisioning other resources that shared this location setting, then you settheir location, too.

Note that if you have anApp Engine app with alocation of eitherus-central oreurope-west, then yourlocation for defaultGoogle Cloud resources is consideredmulti-regional.

Next steps

• To create aCloud Firestore database in a specific location, visitGet started withCloud Firestore.

• For more information about building applications to meet your latency,availability, and durability requirements, refer toGeography and Regions.