Multi Cloud Region Affinity and Latency

AWS, Azure and GCP all are available in many regions. If you need to expand your cloud deployment to a different cloud, you should consider region affinity, that is, select a region of the second cloud that is closest to your current region deployment.

This is a good idea even if you do not need inter cloud connectivity at the moment, because you may need it later and nothing beats minimum latency when it comes to networking and application performance.

For example, if your AWS deployment is in us-east-2 (Ohio), you may think Azure Central US (Illinois) is a good region to deploy. It turns out Azure East US 1 has better latency, at 12ms. The next best region is Azure East US 2, with 16ms latency.

Below is a table that suggests the two best regions in Azure or GCP for a few given AWS regions.

The way to read is the table is for a given region, say AWS us-east-1, the best Azure affinity region is Azure East US 1 with a 1.87ms latency to AWS us-east-1. The second best Azure affinity region is Azure East US 2 with a 6.01ms latency to AWS us-east-1.

AWS Region Azure Affinity Region Latency GCP Affinity Regions Latency
us-east-1 (Virginia) East US 1 (Virginia), 1.87ms us-east4 (Northern Virginia), 1.91ms
  East US 2 (Virginia), 6.01ms us-east1 (South Carolina), 14.14ms
us-east-2 (Ohio) East US 1 (Virginia), 11.84ms us-east4 (Northern Virginia), 11.51ms
  East US 2 (Virginia), 16.52ms us-east1 (South Carolina), 22.98ms
us-west-1 (California) West US 1 (California), 2.17ms us-west2 (California), 8.79ms
  West US 2 (Washington), 24.26ms us-west1 (Oregon), 24.06ms
us-west-2 (Oregon) West US 1 (California), 22.93ms us-west1 (Oregon), 13.22ms
  West US 2 (Washington), 10.78ms us-west2 (California), 27.71ms
eu-central-1 (Frankfurt) West Europe (Netherlands), 10.67ms europe-west3 (Frankfurt), 1.19ms