I'm in Switzerland and have 25 hops, which can be broken into:
- 1-7: Hops within my ISP's in-country network (~4ms total latency)
- 8-10: Hops within my ISP's in-Europe network (~28ms total latency)
- 11: London -> New York (~93ms total latency)
- 12: New York -> Los Angeles (~160ms total latency)
- 13: Transfer in LA from my ISP to AARNet (about the same latency)
- 14: LA to somewhere in NSW (guessing Sydney, 305ms total latency)
- 15-25: Routing within AARNet and Unimelb (319ms total latency)
So most of the latency looks to be attributed to large hops across oceans rather than internal switching. Even if you could narrow it down to London -> NY -> LA -> NSW you'd have 277ms.
From my university network in Germany, I seem to get a direct London → Perth link and a total latency of 278ms. I couldn't find any information about a direct fiber between London and Australia, though there is one from London to Singapore, and AARNet seems to have presence in Singapore. My guess would be that there is some switching below the IP layer going on in Singapore as described by dicknuckle in a sibling comment.
9 cr-fra2-be11.x-win.dfn.de (188.1.144.222) 15.360 ms 15.385 ms dfn.mx1.fra.de.geant.net (62.40.124.217) 15.021 ms
10 ae7.mx1.ams.nl.geant.net (62.40.98.186) 21.806 ms dfn.mx1.fra.de.geant.net (62.40.124.217) 15.244 ms ae7.mx1.ams.nl.geant.net (62.40.98.186) 21.707 ms
11 ae9.mx1.lon.uk.geant.net (62.40.98.129) 29.059 ms ae7.mx1.ams.nl.geant.net (62.40.98.186) 21.805 ms ae9.mx1.lon.uk.geant.net (62.40.98.129) 28.933 ms
12 138.44.226.6 (138.44.226.6) 196.613 ms ae9.mx1.lon.uk.geant.net (62.40.98.129) 29.074 ms 29.156 ms
13 138.44.226.6 (138.44.226.6) 196.807 ms et-7-3-0.pe1.wmlb.vic.aarnet.net.au (113.197.15.28) 277.463 ms 138.44.226.6 (138.44.226.6) 196.778 ms
14 138.44.64.73 (138.44.64.73) 277.544 ms et-7-3-0.pe1.wmlb.vic.aarnet.net.au (113.197.15.28) 277.629 ms *
Yeah you're right, "pe1" shows up in many of their hostnames with different states in the name. And their looking glass shows a bunch of hops within Australia, none of which show up when I do a traceroute.
Huh, my ISP is Init7 and as I said, takes 25 steps to get there, though steps 18-24 inclusive show as "waiting for reply" in MTR.
Init7's traceroute [0] shows 5 fewer steps to r1lon2.core.init7.net than my traceroute though and appears to route through r1bsl1 (assuming Basel) instead of Frankfurt.
Perhaps you're in/near Basel and so skip straight to London, circumventing my 8 hops around Zurich?
Those numbers seem awfully high. I've just ran a speedtest between Germany and California and got 170ms total latency. Back when rabb.it [0] was alive I could even get reaction scores of 450ms compared to 230ms when running the test on my computer. This is quite impressive when you consider that this means video encoding and decoding must happen in less than 50ms. Conventional video encoding is usually slower than real time.
- 1-7: Hops within my ISP's in-country network (~4ms total latency)
- 8-10: Hops within my ISP's in-Europe network (~28ms total latency)
- 11: London -> New York (~93ms total latency)
- 12: New York -> Los Angeles (~160ms total latency)
- 13: Transfer in LA from my ISP to AARNet (about the same latency)
- 14: LA to somewhere in NSW (guessing Sydney, 305ms total latency)
- 15-25: Routing within AARNet and Unimelb (319ms total latency)
So most of the latency looks to be attributed to large hops across oceans rather than internal switching. Even if you could narrow it down to London -> NY -> LA -> NSW you'd have 277ms.