Snowflake's Data Region Strategy in 2027

How many regions Snowflake supports

The count below comes from the rows of the three commercial region tables in Snowflake's Supported cloud regions page, read on October 19, 2026. I counted the rows myself, so treat the totals as a snapshot that will change as Snowflake edits the page.

• North and South America14 regions (AWS 5, Google Cloud 2, Azure 7)
• Europe, Middle East and Africa18 regions (AWS 8, Google Cloud 4, Azure 6)
• Asia Pacific and China17 regions (AWS 11, Google Cloud 1, Azure 5)
• Total commercial regions49 (AWS 24, Azure 18, Google Cloud 7)

AWS is the widest footprint, which fits the company's own filing: the 10-K says a substantial majority of its business runs on AWS. The docs also name regions that are newer or less obvious, such as Mexico Central (Queretaro) on Azure, and Asia Pacific regions in New Zealand, Thailand and Malaysia on AWS.

Two caveats from the docs. Azure North Europe (Ireland) is available only to customers with existing accounts, and new customers there are decided case by case because of Microsoft's requirements. And the China region is run separately by an operating partner, Digital China Cloud Technology Limited, under a separate domain and a separate agreement.

Government and sovereign regions

Snowflake splits U.S. public sector hosting into two kinds, per the same docs page. Some commercial regions carry certain government standards, for example FedRAMP Class C (Moderate) in AWS US East (Commercial Gov - N. Virginia). Compliance with these standards is supported only on Business Critical Edition or higher.

The stricter option is the SnowGov Regions: AWS GovCloud (US) regions us-gov-east-1 and us-gov-west-1, and Azure Government region usgovvirginia. They support standards such as FedRAMP Class D (High), DoW Impact Level 4 and Impact Level 5, and ITAR. Access is limited to U.S. Government Customers or Contractors unless Snowflake agrees otherwise, and you cannot self-provision an initial account; you must contact Snowflake.

Outside the U.S., the docs tie some regions to local assurance programs rather than a separate region family: Canada's CCCS Medium profile, Japan's ISMAP for Tokyo and Osaka, and Australia's IRAP Protected for Sydney. EEA regions have the French health-data HDS certification, which needs supplemental contract terms.

New regions Snowflake has announced

Two official sources show recent additions, and both are worth reading for what they leave out.

• January 30, 2026. Snowflake's release note says three regions became available: Azure East US (Virginia), AWS Middle East (UAE) and Google Cloud Australia Southeast 2 (Melbourne).
• May 27, 2026. In its AWS collaboration press release, Snowflake says it has launches completed or underway in 10 new AWS regions, including New Zealand (Auckland), South Africa (Cape Town), Thailand (Bangkok) and the AWS European Sovereign Cloud, to help customers meet data residency requirements.

The press release names four of the 10 and gives no launch dates for those still underway. The AWS European Sovereign Cloud does not appear in the docs region tables as of October 19, 2026, so treat it as announced, not available. New Zealand, Cape Town and Thailand do appear in the docs list.

What is and is not announced through 2027

Snowflake has not published a region roadmap for 2027, so any list of future regions would be a guess. What can be stated from sources:

• Announced, not confirmed live in the docs: the AWS European Sovereign Cloud and the rest of the 10 AWS regions the press release says are completed or underway.
• Announced as ending: the older Azure Government US Gov Virginia deployment, decommissioned at the beginning of 2027.
• Not announced: specific new regions, dates or counts for 2027, and any Google Cloud or Azure expansion beyond what the docs list today.

The company's own filings explain why the footprint keeps moving. The 10-K lists investments in making the platform available to store and process highly regulated data, and in complying with data sovereignty requirements, among the factors that can affect results. To follow changes, watch the docs release notes and run SHOW REGIONS, which the docs say an organization administrator can use to list available regions.

Replication, Snowgrid and moving data between regions

Because an account lives in one region, multi-region setups work by replication. The replication docs say replication is supported across regions and across cloud platforms, and that all Snowflake regions on AWS, Google Cloud and Azure support it. Database and share replication are available on all editions; replicating other account objects and failover and failback require Business Critical Edition or higher. The docs also say the feature is not available in the People's Republic of China.

Replicating between a commercial region and a government region is a special case: the docs say to contact Snowflake Support to replicate between different region groups.

Snowflake brands this cross-region, cross-cloud layer Snowgrid. Its product page describes sharing data across clouds and regions without ETL, policies and lineage that follow the data, replication for failover, and regional locality controls to keep up with changing regulations. That is Snowflake's marketing description, so check the technical docs for limits.

Cost matters. The data transfer docs say Snowflake charges a per-byte fee when data leaves an account for a different region or a different cloud platform, that transfers within the same region are free, and that there is no ingress fee. Per the replication cost docs, replication charges for data transfer and compute are billed on the target account.

What the SEC filings say about cloud dependence and data residency

Snowflake's 10-K for the year ended January 31, 2026 and its 10-Q for the quarter ended July 31, 2026 give the company's own view of the risks behind its region strategy.

• Cloud provider dependence. Both say Snowflake offers its platform on AWS, Azure and GCP, which are also some of its primary competitors, and that a substantial majority of its business runs on AWS. The 10-K warns a provider could bundle competing products, offer unfavorable pricing, or treat Snowflake differently on terms or regulatory requirements.
• Availability risk. The 10-K says an interruption in a public cloud could cause Snowflake to miss its service-level commitments, and in some cases it may have no contractual right to compensation from the cloud provider.
• Data sovereignty and localization. The risk factors cite the need to adapt and localize the platform for China, Saudi Arabia and other countries because of data sovereignty requirements, and note that Brazil, China and Saudi Arabia have data localization or cross-border transfer laws that could make it harder for customers to replicate their data across jurisdictions.
• Cross-border transfers. The 10-K says that because the business model involves moving data across geographic areas, a material limit on transferring personal data to the United States or other countries could materially affect operations and revenue.

International demand is why this matters. The 10-K says customer accounts outside the United States generated 25% of revenue for the year ended January 31, 2026. The 10-Q says 26% and 25% for the three and six months ended July 31, 2026.

• United States revenue, fiscal year ended January 31, 2026$3,523,974 thousand
• EMEA revenue$763,650 thousand
• Asia-Pacific and Japan revenue$271,044 thousand
• Other Americas revenue$125,278 thousand
• Total revenue$4,683,946 thousand

These are the figures from the 10-K's revenue-by-geography table, based on customer location.

What this means for customers choosing a region

• Pick the region for the rules, not just latency. The docs say regions decide where data is stored and compute runs, and suggest the closest available region if latency matters, noting prices differ by region.
• Plan one account per region. A single account is hosted in a single region, so a multi-region footprint means multiple accounts, usually under one organization.
• Budget the replication bill. Cross-region and cross-cloud transfer carries a per-byte fee, and it lands on the target account.
• Check edition and region limits first. Failover needs Business Critical Edition or higher, government standards need it too, and the China region is separate.
• Do not plan around unannounced regions. Ask your Snowflake representative for written dates before a residency commitment depends on a region that is only announced.

Questions people ask

Sources

• Snowflake docs: Supported cloud regions · Region tables, government regions, one account per region
• Snowflake docs: Jan 30, 2026 new regions · Three regions added
• Snowflake press release: AWS collaboration, May 27, 2026 · 10 new AWS regions completed or underway
• Snowflake Form 10-K, fiscal year ended January 31, 2026 (SEC EDGAR) · Cloud dependence, data sovereignty risks, revenue by geography
• Snowflake Form 10-Q, quarter ended July 31, 2026 (SEC EDGAR) · International revenue share, AWS concentration
• Snowflake docs: Replication and failover across accounts · Cross-region and cross-cloud replication, editions
• Snowflake docs: Understanding data transfer cost · Egress fee between regions and clouds
• Snowflake docs: Understanding replication cost · Replication billed on the target account
• Snowflake: Cross-Cloud Snowgrid · Snowgrid description
• Snowflake docs: Supported cloud platforms · AWS, Azure and Google Cloud hosting

Figures and quotes were read from the linked Snowflake pages and SEC filings on October 19, 2026. The region counts are my own count of the docs tables and will change as Snowflake updates them. This page makes no forecast of future regions.

Top photo: Carl Lender / CC BY 2.0 via Wikimedia Commons