Locations for Realtime Database Stay organized with collections Save and categorize content based on your preferences.
When you provision aRealtime Database instance, you must choose alocation for theinstance. To reduce latency and increase availability, store your data close tothe 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, eachwith its own location setting.
Be aware that once you provision a database instance, you cannot change itslocation setting.
Note: The locations of yourRealtime Database instances donot control the locationsetting of any other resource in your project, includingCloud Firestore databaseinstances orCloud Storage buckets.In the following table, find the supported locations forRealtime Database instancesalong with their associated database URL formats.
| Region name | Region description | Database URL format |
|---|---|---|
us-central1 | Iowa | DATABASE_NAME.firebaseio.com |
europe-west1 | Belgium | DATABASE_NAME.europe-west1.firebasedatabase.app |
asia-southeast1 | Singapore | DATABASE_NAME.asia-southeast1.firebasedatabase.app |
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.