Regions

Neon offers project deployment in multiple AWS and Azure regions. To minimize latency between your Neon database and application, we recommend choosing the region closest to your application server.

AWS regions

• AWS US East (N. Virginia) — aws-us-east-1
• AWS US East (Ohio) — aws-us-east-2
• AWS US West (Oregon) — aws-us-west-2
• AWS Europe (Frankfurt) — aws-eu-central-1
• AWS Asia Pacific (Singapore) — aws-ap-southeast-1
• AWS Asia Pacific (Sydney) — aws-ap-southeast-2

Azure regions

• Azure East US 2 region (Virginia) — azure-eastus2
• Azure Germany West Central region (Frankfurt) — azure-gwc
• Azure West US 3 region (Arizona) — azure-westus3

Request a region

Request a new Provider / Region

Looking for Neon in a different cloud provider or region? Select your preference below, and we'll notify you as soon as it's available.

Request

Select a region for your Neon project

You can select the region for your Neon project during project creation. See Create a project.

All branches and databases created in a Neon project are created in the region selected for the project.

NAT Gateway IP addresses

A NAT gateway has a public IP address that external systems see when private resources initiate outbound connections. Neon uses 3 to 6 IP addresses per region for this outbound communication, corresponding to each availability zone in the region. To ensure proper connectivity for setups such as replicating data to Neon, you should allow access to all the NAT gateway IP addresses associated with your Neon project's region.

If you are unsure of your project's region, you can find this information in the Settings widget on the Project Dashboard.

AWS NAT Gateway IP Addresses

Azure NAT Gateway IP Addresses

Move project data to a new region

Moving a project to a different region requires moving your data using one of the following options:

Option 1: Dump and restore

Using the dump and restore method involves the following steps:

1. Creating a new project in the desired region. For project creation instructions, see Create a project.
2. Moving your data from the old project to the new project. For instructions, see Import data from Postgres.

Moving data to a new Neon project using this method may take some time depending on the size of your data. To prevent the loss of data during the import operation, consider disabling writes from your applications before initiating the import operation. You can re-enable writes when the import is completed. Neon does not currently support disabling database writes. Writes must be disabled at the application level.

Option 2: Logical replication

As an alternative to the dump and restore method described above, you can use logical replication to replicate data from one Neon project to another for a near-zero downtime data migration. For more information, see Replicate data from one Neon project to another.