# Cloud Regions in the United States: AWS, Google Cloud and Azure

> Every AWS, Google Cloud and Azure region in the United States, how six time zones shape off-hours schedules, and which state privacy laws to plan around.

Source: https://zop.dev/cloud-cost-optimization/united-states
Published: 2026-07-01 · Updated: 2026-09-24 · Author: avinash-gaurav · Tags: geo, country, united-states

---

Regions, time zones and data protection law for cloud teams in United States.

The United States has 22 commercial regions across the three providers: four from AWS, nine Google Cloud regions and nine Azure regions, spread from Virginia to Oregon. A team can easily end up in more than one of them, and across more than one time zone.

## Cloud regions in United States

| Provider | Region | Location |
|---|---|---|
| AWS | `us-east-1` | N. Virginia |
| AWS | `us-east-2` | Ohio |
| AWS | `us-west-1` | N. California |
| AWS | `us-west-2` | Oregon |
| Google Cloud | `us-central1` | Council Bluffs, Iowa |
| Google Cloud | `us-east1` | Moncks Corner, South Carolina |
| Google Cloud | `us-east4` | Ashburn, Virginia |
| Google Cloud | `us-east5` | Columbus, Ohio |
| Google Cloud | `us-south1` | Dallas, Texas |
| Google Cloud | `us-west1` | The Dalles, Oregon |
| Google Cloud | `us-west2` | Los Angeles |
| Google Cloud | `us-west3` | Salt Lake City |
| Google Cloud | `us-west4` | Las Vegas |
| Azure | `eastus` | Virginia |
| Azure | `eastus2` | Virginia |
| Azure | `centralus` | Iowa |
| Azure | `northcentralus` | Illinois |
| Azure | `southcentralus` | Texas |
| Azure | `westcentralus` | Wyoming |
| Azure | `westus` | California |
| Azure | `westus2` | Washington |
| Azure | `westus3` | Phoenix |

AWS also runs two GovCloud regions (us-gov-west-1 and us-gov-east-1) in a separate partition for regulated US government workloads. They are not part of the commercial region list above and are accounts of their own.

## Scheduling on local time

Six time zones (seven IANA zones, counting Arizona's America/Phoenix) cover the mainland plus Alaska and Hawaii, and Arizona does not observe daylight saving time, so it drifts an hour against Denver twice a year. A 7 PM Eastern stop fires at 4 PM for a Pacific team. The practical answer is one schedule per team time zone. ZopNight schedules take an IANA time zone, so a 7 PM stop fires at 7 PM in America/Los_Angeles and at 7 PM in America/New_York without anyone converting to UTC.

Time zones: `America/New_York`, `America/Chicago`, `America/Denver`, `America/Phoenix`, `America/Los_Angeles`, `America/Anchorage`, `Pacific/Honolulu`. Currency: USD.

## Data protection law

There is no single federal privacy law. State laws fill the gap, starting with California's Consumer Privacy Act of 2018, as amended by the CPRA in 2020, and other states have passed their own. Check which of them apply to your customers before choosing where their data lives.

Source: [No comprehensive federal law; main state law: California Consumer Privacy Act of 2018 (CCPA), as amended by CPRA (Prop 24, 2020)](https://oag.ca.gov/privacy/ccpa).

## Nearby countries

<a href="https://zop.dev/cloud-cost-optimization/canada">Canada</a>, <a href="https://zop.dev/cloud-cost-optimization/mexico">Mexico</a>. For every country, see <a href="https://zop.dev/cloud-cost-optimization">cloud regions by country</a>.

## Frequently asked questions

### Which US region is cheapest?

It depends on the service and changes with price updates, so compare the provider's current price list for your exact instance types in each candidate region.

### How do I schedule teams in different US time zones?

Create one schedule per time zone. Each ZopNight schedule is pinned to an IANA zone, so the same 8 AM start means 8 AM local for every team.