East US
Read a region profile
The tools connect this region to latency measurements, VM pricing, and IP ranges when those views are available.
Use the region facts and planning sections to review its programmatic name, availability zones, pairing, and access requirements.
East US is part of Azure public cloud, in Virginia, United States. It lists 3 availability zones. Its paired region is West US.
Explore East US
Latency
Published round-trip measurements from East US to 53 other regions.
VM prices
1,429 Linux and 1,356 Windows VM sizes with pay-as-you-go prices in USD. Compare hourly rates and pricing plans in East US.
Compare East US VM pricesIP ranges
570 IPv4 and 197 IPv6 prefixes in AzureCloud.eastus. Inspect or download the regional AzureCloud ranges.
View East US IP rangesRegion facts
- Programmatic name
- eastus
- Location
Virginia, United States
View on Google Maps- Cloud
- Azure public cloud
- Availability zones
- 3 availability zones
- Paired region
- West US
- Approx. opening year
2014
Reported operational year for this location; individual Azure services can have different launch dates.
- Published residency note
Stored at rest in the United States
Microsoft's datacenter summary. Storage and replication behavior depend on the service and configuration.
Regional planning
Pairing and disaster recovery
East US and West US are paired in both directions.
Both regions are in the United States geography.
Published median round-trip latency from East US to West US: 69 ms.
A region pair does not automatically replicate your application or enable failover. Configure recovery for each service you use.
How Azure region pairing worksAccess and service availability
Eligibility: Available to all customers and partners
Available services, VM sizes, and quota still depend on the region and subscription.
Check products available by regionAvailability zone planning
East US: 3 availability zones. West US: No availability zones listed.
Zone support varies by service and VM size. Choose zone-redundant or zonal deployments explicitly; selecting East US alone does not distribute a workload across zones.
Check service and zone supportLowest published latency from East US
The three lowest measured destinations in Microsoft's P50 (median) round-trip dataset. These are Azure backbone measurements; use the browser test for your own connection.
| Destination region | Median round-trip time |
|---|---|
| East US 2 | 8 ms |
| Canada Central | 18 ms |
| North Central US | 19 ms |