AWS provides latency numbers between regions, AZ's and within an AZ in network manager. Useful to have as a latency baseline and to see if they have any issue.
https://docs.aws.amazon.com/network-manager/latest/infrastru...
AWS data center latencies, visualized
31–40 of 223 posts
Re: AWS data center latencies, visualized
#32Us-east-1 is hard to beat. Close to the network centrality of the of the internet, low latency to both the west coast and Europe.
> Close to the network centrality of the of the internet
Most of the Internet is fractured even though technically publically routable. E.g., for someone living in China the US isn't anywhere near "network centrality".
If an internet centrality exists, it is somewhere in France or the Netherlands - usually cross-continent traffic goes through there, they have dedicated interchanges for that.
Re: AWS data center latencies, visualized
#33The data is really useful, and the globe is visually impressive, but it feels like it'd be more practically useful to have a flat world map that shows all the data centers at once and makes it easier to read the lines without them getting excessively close to each other.
A 2D world may not give you the perception of how far some of these locations really are. I think an option to switch between the two would be better.
https://www.greatcirclemap.com has this.
Re: AWS data center latencies, visualized
#34AWS provides latency numbers between regions, AZ's and within an AZ in network manager. Useful to have as a latency baseline and to see if they have any issue. https://docs.aws.amazon.com/network-manager/latest/infrastru...
> AWS provides latency numbers between regions, AZ's and within an AZ in network manager.
AWS also provides dashboards that shows what regions/services are down, and history tells us those are not to be trusted for precisely the same reasons.
Re: AWS data center latencies, visualized
#35AWS provides latency numbers between regions, AZ's and within an AZ in network manager. Useful to have as a latency baseline and to see if they have any issue. https://docs.aws.amazon.com/network-manager/latest/infrastru...
> AWS provides latency numbers between regions, AZ's and within an AZ in network manager. AWS also provides dashboards that shows what regions/services are down, and history tells us those are not to be trusted for precisely the same reasons.
Afaik it also requires someone to manually set it to be down on that page. Pretty sure that nobody is entering latency numbers manually every second, but maybe they have a team for that.
Re: AWS data center latencies, visualized
#36Random fact: I did some planning around this for a client a while ago. While measuring the AWS latencies I found I could get approximate latencies (within 10%) by measuring the rough undersea cable length (km) and dividing by 150. While not overly surprising, it was very consistent. Edit: I think it was actually 155
This page is such a well executed interactive map. Really enjoyed it
Is the math-planation of your random fact basically
(thanks to https://news.ycombinator.com/user?id=Hikikomori for correcting the lightspeed in fibre medium from 3e5 to 2e5 !)
- lightspeed is 2e5 km/s ~ 2e2 km/ms, so/
- length (km) / 200 (km)/ms ~ K length (km) / 200 (km)/ms, so
- latency (ms) ~ K' length (km)
Where K is approximately 1.3 (K' is 1/155) and factors in things like:
- non straight line distance
- networking overhead / switching
- both ways / measurement error
Basically?
Re: AWS data center latencies, visualized
#37Random fact: I did some planning around this for a client a while ago. While measuring the AWS latencies I found I could get approximate latencies (within 10%) by measuring the rough undersea cable length (km) and dividing by 150. While not overly surprising, it was very consistent. Edit: I think it was actually 155
That reminds me of the story of the 500 mile email ( https://www.ibiblio.org/harris/500milemail.html )
Funny story. He must thank the department of statistics for the quick turn around.
Re: AWS data center latencies, visualized
#38Random fact: I did some planning around this for a client a while ago. While measuring the AWS latencies I found I could get approximate latencies (within 10%) by measuring the rough undersea cable length (km) and dividing by 150. While not overly surprising, it was very consistent. Edit: I think it was actually 155
This page is such a well executed interactive map. Really enjoyed it Is the math-planation of your random fact basically ( thanks to https://news.ycombinator.com/user?id=Hikikomori for correcting the lightspeed in fibre medium from 3e5 to 2e5 ! ) - lightspeed is 2e5 km/s ~ 2e2 km/ms, so/ - length (km) / 200 (km)/ms ~ K length (km) / 200 (km)/ms, so - latency (ms) ~ K' length (km) Where K is approximately 1.3 (K' is 1…
Speed of light in a medium like fiber is about 200 000km/s.
Re: AWS data center latencies, visualized
#39Random fact: I did some planning around this for a client a while ago. While measuring the AWS latencies I found I could get approximate latencies (within 10%) by measuring the rough undersea cable length (km) and dividing by 150. While not overly surprising, it was very consistent. Edit: I think it was actually 155
This page is such a well executed interactive map. Really enjoyed it Is the math-planation of your random fact basically ( thanks to https://news.ycombinator.com/user?id=Hikikomori for correcting the lightspeed in fibre medium from 3e5 to 2e5 ! ) - lightspeed is 2e5 km/s ~ 2e2 km/ms, so/ - length (km) / 200 (km)/ms ~ K length (km) / 200 (km)/ms, so - latency (ms) ~ K' length (km) Where K is approximately 1.3 (K' is 1…
It is possible I was measuring latency in a single direction, rather than round-trip-time. My memory is a little hazy now.
Re: AWS data center latencies, visualized
#40Is there something similar for GCP?