Mhmm I would have expected the co-located source/destination numbers to be 1, slightly lower, and 2, more consistent between regions.
Ie, I would not have expected eu-central-1/eu-central-1 to be 1.68ms, and us-east-2/us-east-2 is 8.26ms (almost 5x)
Ie, I would not have expected eu-central-1/eu-central-1 to be 1.68ms, and us-east-2/us-east-2 is 8.26ms (almost 5x)
A geological or technical event near one AWS AZ is highly unlikely to also affect the others of that region, unless the event is regional (heh) in scale. For Google Cloud, the AZs are effectively co-located buildings (or at least, Eemshaven has 3 GC AZ DCs at < 1km distance from each other), making even local disruptions reasonably likely to impact availability for the whole region.
[0] https://docs.aws.amazon.com/ram/latest/userguide/working-wit...