<br />

When you provision aRealtime Databaseinstance, you must choose a*location*for the instance. To reduce latency and increase availability, store your 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 optionally[create multiple databases](https://firebase.google.com/docs/database/usage/sharding)in your project, each with its own location setting.

Be aware that once you provision a database instance, you cannot change its location setting.
| **Note:** The locations of yourRealtime Databaseinstances do*not* control the location setting of any other resource in your project, includingCloud Firestoredatabase instances orCloud Storagebuckets.

In the following table, find the supported locations forRealtime Databaseinstances along with their associated database URL formats.

|  **Region name**  | **Region description** |                            **Database URL format**                             |
|-------------------|------------------------|--------------------------------------------------------------------------------|
| `us-central1`     | Iowa                   | <var translate="no">DATABASE_NAME</var>`.firebaseio.com`                       |
| `europe-west1`    | Belgium                | <var translate="no">DATABASE_NAME</var>`.europe-west1.firebasedatabase.app`    |
| `asia-southeast1` | Singapore              | <var translate="no">DATABASE_NAME</var>`.asia-southeast1.firebasedatabase.app` |