Traceroute

Polchraine · Nov 13, 2012, 12:29:45

I am trying to sort out some problems that members of another forum are having and need to gather some traceroute information from various ISPs.

Please could I ask if members here could run a traceroute for me and then either PM the results through to me, or add them to the thread. Please remove the IP address from the first two hops - which would correspond to your local network and public IP, replacing them with rrr.rrr.rrr.rrr

The destination is www.full-bore.co.uk

1 * * * Request timed out.
2 13 ms 12 ms 12 ms 10.0.0.1
3 12 ms 12 ms 13 ms 192.168.201.90
4 13 ms 13 ms 12 ms 192.168.134.2
5 12 ms 12 ms 12 ms 192.168.71.13
6 13 ms 15 ms 13 ms 192.168.69.252
7 13 ms 12 ms 12 ms 217.39.0.2
8 13 ms 13 ms 13 ms 213.120.178.41
9 13 ms 13 ms 15 ms acc2-10GigE-0-0-0-0.l-far.21cn-ipp.bt.net [109.159.249.120]
10 21 ms 13 ms 15 ms core1-te0-7-0-4.faraday.ukcore.bt.net [109.159.249.33]
11 13 ms 13 ms 13 ms peer2-xe8-1-0.telehouse.ukcore.bt.net [109.159.255.101]
12 13 ms 13 ms 13 ms 195.99.126.129
13 14 ms 14 ms 14 ms iomart.londra32.lon.seabone.net [89.221.43.106]
14 14 ms 15 ms 14 ms 593.net1.north.dc5.as20860.net [62.233.127.174]
15 15 ms 16 ms 15 ms 87.117.211.46
16 16 ms 15 ms 15 ms cpanel.full-bore.co.uk [5.77.45.227]

The first look a little odd as I am using an Openzone hotspot and the 192.168.xxx.xxx are in a local network before breakout.

Steve · Nov 13, 2012, 13:24:12

Traceroute has started...

traceroute to full-bore.co.uk (5.77.45.227), 64 hops max, 72 byte packets
1 home.gateway.home.gateway (192.168.1.254) 1.816 ms 1.718 ms 1.643 ms
2 telehouse-gw4-lo1.idnet.net (212.69.63.98) 17.588 ms 17.810 ms 20.181 ms
3 telehouse-gw6-gi3-401.idnet.net (212.69.63.182) 18.532 ms 17.884 ms 16.885 ms
4 te8-4.core1.thn.as20860.net (195.66.224.207) 17.750 ms 17.442 ms 19.142 ms
5 593.net1.north.dc5.as20860.net (62.233.127.174) 20.122 ms 18.546 ms 18.404 ms
6 87.117.211.46 (87.117.211.46) 19.103 ms 33.141 ms 18.299 ms
7 cpanel.full-bore.co.uk (5.77.45.227) 18.833 ms 19.591 ms 22.112 ms

Glenn · Nov 13, 2012, 13:30:47

I would try from work, but it's timing out after the 3rd hop. There are ongoing proxy issues here this week.

andrue · Nov 13, 2012, 13:43:54

From our office connection (Timico)

3 2 ms 1 ms 1 ms ip-rrrrrrr.dsl.twang.net [rr.rr.rr.rr] (oooh arrrr)
4 26 ms 33 ms 26 ms lo5.the-lns2.router.timico.net [62.121.9.205]
5 95 ms 45 ms 27 ms vl917.tch-edge2.uk.timico.net [62.121.12.22]
6 26 ms 26 ms 100 ms te8-4.core1.thn.as20860.net [195.66.224.207]
7 98 ms 27 ms 27 ms 593.net1.north.dc5.as20860.net [62.233.127.174]
8 28 ms 29 ms 28 ms 87.117.211.46
9 29 ms 27 ms 27 ms cpanel.full-bore.co.uk [5.77.45.227]

For what it's worth the same connection to my home (IDNet) connection is:

3 2 ms 1 ms 1 ms ip-rrrrrrr.dsl.twang.net [rr.rr.rr.rr]
4 26 ms 27 ms 30 ms lo5.the-lns2.router.timico.net [62.121.9.205]
5 45 ms 26 ms 27 ms vl917.tch-edge2.uk.timico.net [62.121.12.22]
6 26 ms 26 ms 26 ms idnet-gw-a.lonap.net [193.203.5.132]
7 27 ms 27 ms 26 ms telehouse-gw4-gi0-1-400.idnet.net [212.69.63.244]
8 37 ms 38 ms 37 ms rrrrrr.me.uk [rr.rr.rr.rr]

JB · Nov 13, 2012, 13:53:42

Tracing route to full-bore.co.uk [5.77.45.227]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms nnn.nnn.nnn.nnn
2 12 ms 11 ms 12 ms losubs.subs.dsl2.wh-man.zen.net.uk [62.3.87.147]
3 12 ms 11 ms 11 ms xe-0-3-0-115.cr2.wh-man.zen.net.uk [62.3.87.185]
4 15 ms 13 ms 14 ms ge-3-0-0-0.cr1.kp-leeds.zen.net.uk [62.3.80.58]
5 17 ms 15 ms 13 ms ge-3-1-0-0.cr2.kp-leeds.zen.net.uk [62.3.80.74]
6 19 ms 19 ms 19 ms ge-3-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.78]
7 19 ms 77 ms 18 ms ge-2-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.42]
8 18 ms 18 ms 19 ms te8-4.core1.thn.as20860.net [195.66.224.207]
9 19 ms 20 ms 20 ms 593.net1.north.dc5.as20860.net [62.233.127.174]
10 21 ms 20 ms 20 ms 87.117.211.46
11 20 ms 19 ms 21 ms cpanel.full-bore.co.uk [5.77.45.227]

Trace complete.

andrue · Nov 13, 2012, 16:22:51

From home:

2 11 ms 11 ms 12 ms telehouse-gw4-lo1.idnet.net [212.69.63.98]
3 11 ms 11 ms 11 ms telehouse-gw6-gi4-400.idnet.net [212.69.63.246]
4 99 ms 30 ms 48 ms te8-4.core1.thn.as20860.net [195.66.224.207]
5 12 ms 12 ms 13 ms 593.net1.north.dc5.as20860.net [62.233.127.174]
6 13 ms 13 ms 13 ms 87.117.211.46
7 13 ms 12 ms 13 ms cpanel.full-bore.co.uk [5.77.45.227]

armadillo · Nov 13, 2012, 17:22:34

From home

Tracing route to full-bore.co.uk [5.77.45.227]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms nnn.nnn.nnn.nnn
2 32 ms 32 ms 31 ms telehouse-gw4-lo1.idnet.net [nnn.nnn.nnn.nnn]
3 30 ms 31 ms 31 ms telehouse-gw6-gi4-400.idnet.net [212.69.63.246]

4 31 ms 31 ms 30 ms te8-4.core1.thn.as20860.net [195.66.224.207]
5 32 ms 35 ms 36 ms 593.net1.north.dc5.as20860.net [62.233.127.174]

6 32 ms 32 ms 33 ms 87.117.211.46
7 32 ms 32 ms 32 ms cpanel.full-bore.co.uk [5.77.45.227]

Baz · Nov 13, 2012, 20:45:21

1
2 30 ms 29 ms 29 ms telehouse-gw3-lo1.idnet.net
3 29 ms 29 ms 29 ms telehouse-gw6-gi4-400.idnet.net [212.69.63.246]

4 29 ms 29 ms 60 ms te8-4.core1.thn.as20860.net [195.66.224.207]
5 30 ms 30 ms 30 ms 593.net1.north.dc5.as20860.net [62.233.127.174]

6 31 ms 31 ms 31 ms 87.117.211.46
7 30 ms 30 ms 31 ms cpanel.full-bore.co.uk [5.77.45.227]

trace complete.

Polchraine · Nov 14, 2012, 16:41:34

Thanks all of you. Looks as though none of you had issues.