Supported Regions

Snowflake lets your organization choose where your data is geographically stored across your regional, national, and international operations. Regions also determine where your compute resources are provisioned. Snowflake supports multiple regions for all supported cloud platforms.

You can choose to have multiple accounts in separate regions to address global latency concerns and/or provide additional backup and disaster recovery support beyond the standard support provided by Snowflake. For US government agencies, Snowflake provides a dedicated region that meets the specific privacy and security requirements of the US government.

Note that regions do not limit user access to Snowflake; they only dictate the geographic location where data is stored and compute resources are provisioned.

Important

Each Snowflake account is located in a single region (i.e. multi-region accounts are not supported).

In addition, Snowflake does not yet support accessing or sharing data between regions. If you wish to use Snowflake across multiple regions, you must maintain a separate Snowflake account in each region.

In this Topic:

List of Regions

Snowflake currently supports the following regions, with more planned for the future:

Cloud / Region

Region ID

Notes

Amazon Web Services (AWS)

US East (N. Virginia)

us-east-1

US East (Ohio)

us-east-2

US West (Oregon)

us-west-2

Region ID is required only when configuring AWS PrivateLink for accounts in US West.

Canada (Central)

ca-central-1

EU (Ireland)

eu-west-1

EU (Frankfurt)

eu-central-1

Asia Pacific (Singapore)

ap-southeast-1

Asia Pacific (Sydney)

ap-southeast-2

Google Cloud Platform (GCP)Preview

us-central1 (Iowa)

us-central1

Microsoft Azure

East US 2

east-us-2

US Gov Virginia

us-gov-virginia

Available only for accounts on Business Critical (or higher).

Canada Central

canada-central

West Europe

west-europe

Australia East

australia-east

Southeast Asia

southeast-asia

Note

Snowflake features and services are identical across regions; however, there are some differences in unit costs for credits and data storage. In addition, another factor that impacts unit costs is whether your Snowflake account is On Demand or Capacity.

For more information about pricing as it pertains to a specific region and account type, see the pricing page (on the Snowflake website).

North American (US and Canada) Regions

Snowflake supports the following regions in the US and Canada:

AWS
  • US West (Oregon)

  • US East (N. Virginia)

  • US East (Ohio)

  • Canada (Central)

GCP
  • us-central1 (Iowa)

Azure
  • East US 2

  • US Gov Virginia

  • Canada Central

Support hours

(applies only to Snowflake Standard Edition; all other editions have 24/7 support)

Monday - Friday, 6:00 AM - 6:00 PM Pacific Time (PST or PDT)

If your account is hosted on AWS and latency is a concern, you should choose the available region with the closest geographic proximity to your end users.

Note

US Gov Virginia is offered on Microsoft Azure Government, a dedicated cloud that is operated by screened U.S. citizens and is available only to U.S. government agencies and their partners.

The US Gov Virginia region supports Snowflake accounts using Business Critical Edition (or higher).

European Union (EU) Regions

Snowflake supports the following EU regions:

AWS
  • EU (Ireland)

  • EU (Frankfurt)

Azure
  • West Europe

Support hours

(applies only to Snowflake Standard Edition; all other editions have 24/7 support)

Monday - Friday, 6:00 AM - 6:00 PM Central Europe Time (CEST or CEDT)

These regions are supported for organizations that prefer or require their data to be stored in the European Union. Multiple regions are provided to allow organizations to meet their individual compliance and data sovereignty requirements. Snowflake does not move data between accounts, so any data in an account in an EU region will be maintained in this region only, unless explicitly copied or moved by users.

If latency is a concern, you should choose the available EU region with the closest geographic proximity to your end users; however, this may have cost implications, due to pricing differences between the regions. For more details, see the pricing page (in the Snowflake website).

Asia Pacific Regions

Snowflake provides the following Asia Pacific regions:

AWS
  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

Azure
  • Australia East

  • Southeast Asia

Support hours

(applies only to Snowflake Standard Edition; all other editions have 24/7 support)

Monday - Friday, 6:00 AM - 6:00 PM Australian Eastern Time (AEST or AEDT)

These regions are supported for organizations that prefer or require their data to be stored in Southeast Asia or Australia. Snowflake does not move data between accounts, so any data in an account in an Asia Pacific region will be maintained in this region only, unless explicitly copied or moved by users.

Specifying Region Information in Your Hostname

A hostname for a Snowflake account starts with an account name (provided by Snowflake) and ends with the Snowflake domain (snowflakecomputing.com):

account_name.snowflakecomputing.com

However, note that your full account name may include additional segments that identify the region and cloud platform where your account is hosted.

Account name examples by region

If your account name is xy12345:

Cloud Platform / Region

Full Account Name

AWS

US East (N. Virginia)

xy12345.us-east-1

US East (Ohio)

xy12345.us-east-2.aws

US West (Oregon)

xy12345

Canada (Central)

xy12345.ca-central-1.aws

EU (Ireland)

xy12345.eu-west-1

EU (Frankfurt)

xy12345.eu-central-1

Asia Pacific (Singapore)

xy12345.ap-southeast-1

Asia Pacific (Sydney)

xy12345.ap-southeast-2

GCPPreview

us-central1 (Iowa)

xy12345.us-central1.gcp

Azure

East US 2

xy12345.east-us-2.azure

US Gov Virginia

xy12345.us-gov-virginia.azure

Canada Central

xy12345.canada-central.azure

West Europe

xy12345.west-europe.azure

Australia East

xy12345.australia-east.azure

Southeast Asia

xy12345.southeast-asia.azure

Important

If either of the following conditions is true, your account name is different than the structure described in this example:

  • If your Snowflake Edition is VPS, please contact Snowflake Support for details about your account name.

  • If AWS PrivateLink is enabled for your account, your account name requires an additional privatelink segment. For more details, see AWS PrivateLink & Snowflake.