Tracert results

Reading a post in the Plusnet forum made me run some tests on my Bt Infinity setup.

These are the tracerts I normally get; first at 18:40 last evening and the second at 9:15 this morning.

Could I get better from my, wired, BT HH4 connected to my Win 7 Home premium pc?

Microsoft Windows [Version 6.1.7601]
at 18:40 10 02 2015



Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\****>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:


1 1 ms <1 ms <1 ms BThomehub.home [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 16 ms 16 ms 16 ms 31.55.186.152
5 15 ms 15 ms 15 ms 195.99.127.38
6 15 ms 15 ms 15 ms host213-121-193-131.ukcore.bt.net [213.121.193.1
31]
7 16 ms 16 ms 16 ms 194.74.65.42
8 * * * Request timed out.
9 17 ms 16 ms 17 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
10 18 ms 18 ms 17 ms 132.185.255.165
11 16 ms 16 ms 16 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]

Trace complete.

at 09:15 11 02 2015


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\****>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms BThomehub.home [192.168.1.254]
2 * * * Request timed out.
3 * 16 ms 15 ms 31.55.186.129
4 16 ms 16 ms 16 ms 31.55.186.152
5 16 ms 15 ms 15 ms 195.99.127.38
6 15 ms 15 ms 15 ms peer2-xe8-2-0.telehouse.ukcore.bt.net [213.121.1
93.131]
7 16 ms 16 ms 16 ms 194.74.65.42
8 * * * Request timed out.
9 16 ms 17 ms 17 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
10 17 ms 17 ms 17 ms 132.185.255.165
11 16 ms 16 ms 16 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]

Trace complete.

Without knowing which part of the UK you are based in hard to say, e.g. those would be very low latency if you are in Scotland

East London; Romford

Reading the Plusnet forum hop 2 was 14ms and considered "a bit high" whereas as mine is " * * * Request timed out." is that ok?

Different ISP so the route and visible hops will be different.

Some providers configure some hops to not respond to tracert requests too (hence the *'s)

So 16ms is reasonable, yes some people get better, but yours is probably 16ms because your FTTC has some interleaving turned on to reduce the number of errors and thus stalls in day to day use.

If you are a gamer trying for the lowest latency, then better to lose 1 to 2 ms and gain a stable performance, than chance 8ms latency that stalls to 40ms every few minutes.

In reply to a post by athegn:

Reading the Plusnet forum hop 2 was 14ms and considered "a bit high" whereas as mine is " * * * Request timed out." is that ok?

Yes, that's fine. You're reaching the BBC in 16ms.

Varying times in a tracert are normal, and only the destination one really matters as long as that stays stable.

On the other hand, a significant step up on one of the intermediate hops that is then maintained for all subsequent hops indicates a bottleneck at that hop.

Thanks all

This link shows my main problem. This winter has been better than previous; suspect council works have improved drainage in area:-

http://forums.thinkbroadband.com/bt/t/4283367-will-i...

What's that got to do with a tracert?

Edited by BatBoy (Wed 11-Feb-15 17:20:01)

In reply to a post by BatBoy:

In reply to a post by athegn:

Reading the Plusnet forum hop 2 was 14ms and considered "a bit high" whereas as mine is " * * * Request timed out." is that ok?

Yes, that's fine. You're reaching the BBC in 16ms.

Yeah we are getting similar latency as well with BT shown below:

Tracing route to bbc.co.uk [212.58.244.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  BTHUB4 [192.168.2.253]
  2    15 ms    15 ms    15 ms  217.32.146.73
  3    14 ms    15 ms    14 ms  217.32.146.126
  4    15 ms    16 ms    16 ms  217.32.147.194
  5    16 ms    16 ms    16 ms  217.41.168.13
  6    15 ms    15 ms    17 ms  217.41.168.107
  7    16 ms    16 ms    24 ms  acc1-te0-0-0-21.l-far.21cn-ipp.bt.net [109.159.249.94]
  8    17 ms    15 ms    15 ms  core3-te0-2-0-19.faraday.ukcore.bt.net [109.159.249.5]
  9    16 ms    15 ms    15 ms  peer2-xe8-0-1.telehouse.ukcore.bt.net [109.159.254.179]
 10    16 ms    15 ms    16 ms  194.74.65.42
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    16 ms    17 ms    17 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
 14    17 ms    17 ms    16 ms  132.185.255.149
 15    16 ms    15 ms    16 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.

However with Sky we get to the bbc site in less hops but more latency shown below:

Tracing route to bbc.co.uk [212.58.244.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.254
  2     *        *        *     Request timed out.
  3    37 ms    37 ms    39 ms  ip-84-38-37-44.easynet.co.uk [84.38.37.44]
  4    36 ms    36 ms    37 ms  ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.189]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    38 ms    38 ms    35 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
  8    36 ms    36 ms    37 ms  132.185.255.149
  9    36 ms    37 ms    36 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.

Paul