understanding tracert?

sandyman80

I have just had SKY FTTP broadband installed and there is sometimes a 2 or 3 second lag before I can connect to google dot com and other sites.

I did a tracert and this is the result

>tracert www.google.com

Tracing route to www.google.com [2a00:1450:4009:826::2004]

over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  2a02:c7c:cbc5:e900::1

  2     *        *        *     Request timed out.

  3    15 ms    14 ms    61 ms  2001:4860:1:1:0:15e7:0:d

  4    15 ms    14 ms    14 ms  2001:4860:1:1:0:15e7:0:c

  5    13 ms    12 ms    12 ms  2a00:1450:8135::1

  6    13 ms    13 ms    14 ms  2001:4860:0:1::54c6

  7    14 ms    13 ms    14 ms  2001:4860:0:1::7dfe

  8    15 ms    14 ms    15 ms  2001:4860::c:4002:aff6

  9    16 ms    16 ms    15 ms  2001:4860::9:4001:2717

 10    14 ms    13 ms    13 ms  2001:4860:0:1::73c7

 11    13 ms    14 ms    13 ms  lhr48s48-in-x04.1e100.net [2a00:1450:4009:826::2004]

every time I do  this the second request times out.

I tried phoning Sky but I cannot get to speak to someone 

Peter999_2

The tracert looks fine, nothing unusual in it.     The second hop is probably your ISPs edge router which refuses to reply to a ping or tracert request - this is perfectly normal.

Have you tried changing your DNS server to either 1.1.1.1 (cloudflare), 8.8.8.8 (google) to see if it is faster?
Have you tried temporarily disabling IPv6 to see if there is any difference?

TadleyBaggie

As above, having timed out requests is quite normal. Some devices/servers are set to ignore ping requests.