If worst-case is an option, there are some interesting routing policies between certain places.
One example is a Australia to China--take Perth to Chongqing as an example. They're at about the same longitude, but RTT is routinely greater than 500 ms. Packets travel to Singapore, then cross the entire Pacific ocean to the west coast of the US, and back, before making it back to China. Try it for yourself from this Perth-based looking glass[1]. PING 117.151.152.239 (117.151.152.239) 56(84) bytes of data. 64 bytes from 117.151.152.239: icmp_seq=1 ttl=236 time=511 ms 64 bytes from 117.151.152.239: icmp_seq=2 ttl=236 time=522 ms traceroute to 117.151.152.239 (117.151.152.239), 30 hops max, 60 byte packets 1 172.18.0.1 (172.18.0.1) 0.021 ms 0.004 ms 0.004 ms 2 45.248.78.65 (45.248.78.65) 0.611 ms 0.696 ms 0.777 ms 3 45.248.78.139 (45.248.78.139) 0.678 ms 0.818 ms 0.959 ms 4 core.p1.wa.hostuniversal.com.au (103.216.222.7) 0.145 ms 0.165 ms 0.195 ms 5 be6745.201.ccr51.per01.atlas.cogentco.com (154.18.100.65) 0.468 ms 0.418 ms 0.496 ms 6 be2428.ccr31.sin01.atlas.cogentco.com (154.54.88.138) 46.625 ms 46.659 ms 46.691 ms 7 be2913.ccr41.lax04.atlas.cogentco.com (154.54.27.54) 218.213 ms 237.901 ms 237.959 ms [...] 1: https://perth-lg.ransomit.com.au/ Sean Donelan <s...@donelan.com> writes: > What is the current estimated diameter of the Internet? > > Maximum (worst-case) RTT edge-to-edge? > > Most public latency data is now edge-to-cloud, not edge-to-edge. > Cloud engineers have done a great job, and edge-to-cloud less than > 1-sec RTT. > > Where have the long-slow pipes gone? > > https://www.cloudping.co/grid > > https://learn.microsoft.com/en-us/azure/networking/azure-network-latency?tabs=Americas%2CWestUS > > https://www.verizon.com/business/terms/latency/
