I thought Australia sucked until I checked the latencies for South America and South Africa. Not a single "good" latency link =)

Cool, but information about what links were used would be nice. I assume it's latencies for default AWS links, which you likely won't use if you _care_ about the latency.

I worked at a military company and we made a SIEM tool to use at government facilities. Our Director, which was an ex-colonel at Miltiary IT, found that login screen is too plain and we need to have a world spinning. So we've implemented the end of Terminator 3 nukes over globe screen in WebGL to please him. This reminds me of it.

Anyways, although this looks cool, it'd be much more easily understandable in a 2d map instead of a rotating one.

It is insane to see this and conceptualize that you can send data across the world and back in under 500ms. Imagine telling someone that 100 years ago.

Its a bit sad, we have one of the Swedish, actual physical buildings for AWS in my town. But of course the traffic does not exit here, but is instead aggregated between the different sites spread around cities regionally. So no sub-ms latencies for me towards that center. I think the traffic basically went a couple hundred kms before turning back here.

Some AWS data center latencies, there are many missing: https://aws.amazon.com/about-aws/global-infrastructure

Technically speaking those aren’t datacenters, they’re regions. AWS regions can have multiple AZs, and each AZ can have multiple datacenters spread around a city, each with different latency characteristics. This is completely opaque to customers, you don’t really get to choose which one you’re in. There are ways to gain info about it though.

This is way outdated now but gives a rough idea: https://wikileaks.org/amazon-atlas/document/AmazonAtlas_v1/A...

Source: did some latency work for a market maker.

This jives with measurements I've done before. I ended up running a ping setup for a few months from every region to every other region to get these timings. I was using it to calculate what our GQL latencies would look like if the backing servers were in another region or in the same region as a way to start regionalization work. Sadly we had to depend on those latencies so much that it was deemed a non-starter of an approach. Even us-west-2 (home) to us-east-2 took us from p99 300ms to p99 2.4 seconds. That sweet sweet latency reduction.

This is really cool, wish there were something like it for Azure as well.

Wow! This is so cool. Thank you so much for sharing!

I used my own tool Livedocs to visualize the same and here are the results. https://livedocs.com/livedocs/aws-latencies-3f2fefd5-f45d-48...