Is Your ISP Connection Ping Longer than It Should Be?

• 

  oscargamer on 26/04/2019 - 14:59

  My ping is 26ms to google

• 

  salmon123 on 26/04/2019 - 15:02

  Can you post your traceroute to another google.com.au IP? eg 216.58.199.35

  I actually see the 13ms hop to 172.217.25.142 as well … I'm using TPG business fibre at work. The other IPs don't have it though!

  • 

    bpop99 on 26/04/2019 - 16:33

    This is the one for 216.58.199.35. It still seems the same. I mean, its literally either the TPG server is thousands of kms away or the packet is sitting at the server for some reason before heading out.. Funny thing is that every other hop is under a millisecond.

    PING 216.58.199.35 (216.58.199.35): 56 data bytes
    64 bytes from 216.58.199.35: icmp_seq=0 ttl=56 time=14.749 ms
    64 bytes from 216.58.199.35: icmp_seq=1 ttl=56 time=14.816 ms
    64 bytes from 216.58.199.35: icmp_seq=2 ttl=56 time=14.543 ms
    64 bytes from 216.58.199.35: icmp_seq=3 ttl=56 time=13.791 ms
    64 bytes from 216.58.199.35: icmp_seq=4 ttl=56 time=14.385 ms
    64 bytes from 216.58.199.35: icmp_seq=5 ttl=56 time=15.534 ms
    64 bytes from 216.58.199.35: icmp_seq=6 ttl=56 time=23.857 ms
    64 bytes from 216.58.199.35: icmp_seq=7 ttl=56 time=13.725 ms
    ^C
    —- 216.58.199.35 ping statistics —-
    8 packets transmitted, 8 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 13.725/15.675/23.857/3.140 ms

    traceroute to 216.58.199.35 (216.58.199.35), 64 hops max, 52 byte packets
    1 192.168.1.1 (192.168.1.1) 1.623 ms 1.225 ms 0.908 ms
    2 10.20.25.5 (10.20.25.5) 13.715 ms 13.007 ms 13.028 ms
    3 syd-gls-har-agr11-be-14.tpgi.com.au (202.7.205.29) 14.254 ms 13.299 ms 13.705 ms
    4 syd-gls-har-dom1-be200.tpgi.com.au (203.221.3.69) 14.393 ms
    syd-gls-har-dom1-be100.tpgi.com.au (203.221.3.5) 21.253 ms 14.654 ms
    5 72.14.197.162 (72.14.197.162) 13.855 ms 14.428 ms 13.805 ms
    6 108.170.247.33 (108.170.247.33) 14.897 ms 15.056 ms 14.333 ms
    7 209.85.243.243 (209.85.243.243) 14.023 ms
    209.85.243.145 (209.85.243.145) 13.954 ms 13.612 ms
    8 syd09s12-in-f35.1e100.net (216.58.199.35) 13.762 ms 14.129 ms 15.380 ms

    • 

      salmon123 on 26/04/2019 - 16:55

      Looks like my 13ms hop to 172.217.25.142 has disappeared now.

      The fact that I didn't see it to the other host, indicates, to me that there's probably a capacity issue (or other fault) in the TPG network somewhere.

      • 

        Toons on 26/04/2019 - 17:15

        +1

        There has been issues with some of the sub sea trunklines there has also been a tie in of a new main line through into Asia so yes to both I guess more traffic through other networks because of others being down or running reduced capacity.

        Sydney unfortunately had been taking the bulk of traffic which seems ridiculous

        I get a 9ms ping consistently but I've seen it climb I've also got a snip of my upload speed outperforming my download speed which someone said was impossible till I showed them haven't heard from them since.

        The only thing I normally play with unless I want to bypass something is change DNS I use googles servers but I hear that cloudflare is faster again for those that want to squeeze everything out of the line.

        • 

          bpop99 on 26/04/2019 - 19:36

          @Toons: Your results if 9ms is bang on the range of what it should be for ADSL - I've already changed my dns to cloudfare, but whatever this server does, its adding somewhat of a delay.

• 

  Trung on 26/04/2019 - 16:28

  Majority of your latency is not due to distance, it's due to processing delays.
  The slowest point is between your modem to the ADSL exchange, which might only be a few kilometres away.
  From there on, it's a lot faster through optical fibres and high speed routers, etc.

  • 

    bpop99 on 26/04/2019 - 16:47

    I think you may be right about processing delays, though this is quite surprising. I would have expected pinging a server residing in Sydney to take under 10ms. I only noticed how high it was when trying to put a firewall in between seemed to cause the latency to jump significantly, and also as I came back from another country where local server pings (such as running a speedtest to the nearest server) tended to be closer to 5ms(admittedly that was on fibre).

• 

  slow on 26/04/2019 - 16:29

  less than 20ms is pretty good and you will never get much lower than that through an ISP

  • 

    bpop99 on 26/04/2019 - 16:55

    I guess we are conditioned to set the bar quite low when it comes to internet, but my feeling is that this adds up, especially if accessing foreign websites or adding another hop due to using a VPN. I'm just not sure if its normal - as i mentioned, 13 ms is like the signal travelling the equivalence of 3000 kms (if i've got my maths right).

    I'm not surprised that it took that amount of time to reach google, I'm surprised that amount of time to reach just the ISP. While speed is important, latency is really the deal when it comes to videos chats and gaming.