Is Your ISP Connection Ping Longer than It Should Be?
Hey all, I'm curious if this is an issue for you guys - I'm on TPG ADSL and I noticed a very peculiar thing about ping times. This is not an issue per se, but still something that I feel shouldn't be the case
I was dabbling in some networking stuff several weekends ago and realised that what I did was adding delay to the packets. At that time i thought maybe it was what I was doing. However, now that I have removed it and my connection is back to being connected directly to the router/modem, i realised that ping times t0 the TPG servers are quite long. More specifically, the single hop from my router to the ISP takes up 80-90% of the time for the packet to reach its destination.
Pinging google.com takes about 14 - 16 milliseconds, and running a tracert / traceroute indicates that the bulk of that time taken is that single hop to the ISP. Here are the results:
PING google.com (22.214.171.124): 56 data bytes
64 bytes from 126.96.36.199: icmp_seq=0 ttl=56 time=15.122 ms
64 bytes from 188.8.131.52: icmp_seq=1 ttl=56 time=15.375 ms
64 bytes from 184.108.40.206: icmp_seq=2 ttl=56 time=17.055 ms
64 bytes from 220.127.116.11: icmp_seq=3 ttl=56 time=15.449 ms
traceroute to google.com (18.104.22.168), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 2.056 ms 0.998 ms 0.922 ms
2 10.20.25.5 (10.20.25.5) 12.664 ms 14.066 ms 13.567 ms
3 syd-apt-ros-agr11-be-24.tpgi.com.au (22.214.171.124) 13.024 ms 13.378 ms 13.784 ms
4 syd-apt-ros-dom1-be-20.tpgi.com.au (126.96.36.199) 20.626 ms
syd-apt-ros-dom1-be-10.tpgi.com.au (188.8.131.52) 18.772 ms
syd-apt-ros-dom1-be-20.tpgi.com.au (184.108.40.206) 19.571 ms
5 220.127.116.11 (18.104.22.168) 14.400 ms 14.425 ms 14.569 ms
6 22.214.171.124 (126.96.36.199) 14.771 ms 21.858 ms
188.8.131.52 (184.108.40.206) 15.285 ms
7 220.127.116.11 (18.104.22.168) 13.777 ms 14.888 ms
22.214.171.124 (126.96.36.199) 14.870 ms
8 syd15s03-in-f14.1e100.net (188.8.131.52) 14.296 ms 14.497 ms 14.598 ms
In the grand scheme of things this may not seem like much. But 13 ms in delay essentially means its hopping to a server about 3000kms away, or some form of delay in the equipment/software they use, which is weird. I stay in Sydney, so I would expect they would have their servers nearby. You can imagine that this may not be a big deal for the average use but again, this is not normal and you would notice that it is only this one hop that consumes the majority of the time it takes to reach google's servers
Does anyone have an explanation for this?