cancel
Showing results for 
Search instead for 
Did you mean: 
yy
Beginner
1,427 Views
Message 1 of 3

Can anyone interpret this trace for me please

I've had an ongoing issue for about 10 months which looks to me like data loss at peak times. I've got BT working on this but it's a slow and painful process. Outbound tracert from me to an IP address are fine and show slow times but no data loss. I've just done a couple of reverse Trace Routes (Tracert) i.e. in to my public IP rather than out from my computer and got the results below. What I don't know is whether they are reaching me and being blocked by the firewall or whether they are failing before they get to me. An IP lookup shows the last successful  addresses are BT infrastructure servers but I can't tell whether they are at my local exchange or not. Thanks in advance.

 

Here are the 2 sets of results:

 

Test 1 - Run by a friend

 

Tracing route to host86-150-49-122.range86-150.btcentralplus.com [86.150.49.122]

over a maximum of 30 hops:

 

  1     1 ms    <1 ms    <1 ms  192.168.0.1

  2    39 ms    37 ms    38 ms  cr4.clber.uk.easynet.net [87.87.253.223]

  3    33 ms    33 ms    33 ms  fe3-1-3.ar11.bllon.uk.easynet.net [82.111.96.81]

  4    34 ms    32 ms    33 ms  te0-2-0-2.er11.thlon.ov.easynet.net [89.200.131.89]

  5    34 ms    34 ms    33 ms  linx7.ukcore.bt.net [195.66.224.56]

  6    48 ms    44 ms    74 ms  core1-te-0-3-1-0.ealing.ukcore.bt.net [62.172.102.2]

  7    38 ms    37 ms    37 ms  acc1-10GigE-0-1-0-0.l-far.21cn-ipp.bt.net [109.159.249.16]

  8    39 ms    38 ms    38 ms  109.159.249.100

  9    36 ms    37 ms    37 ms  213.120.176.177

 10    40 ms    45 ms    37 ms  213.120.176.21

 11    44 ms    46 ms    41 ms  213.120.177.25

 12     *        *        *     Request timed out.

 13     *        *        *     Request timed out.

 14     *        *        *     Request timed out.

 15     *        *        *     Request timed out.

 16     *        *        *     Request timed out.

 17     *        *        *     Request timed out.

 18     *        *        *     Request timed out.

 19     *        *        *     Request timed out.

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

 22     *        *        *     Request timed out.

 23     *        *        *     Request timed out.

 24     *        *        *     Request timed out.

 25     *        *        *     Request timed out.

 26     *        *        *     Request timed out.

 27     *        *        *     Request timed out.

 28     *        *        *     Request timed out.

 29     *        *        *     Request timed out.

 30     *        *        *     Request timed out.

 

Trace complete.

 

Test 3 - Conducted from the internet

http://centralops.net/co/Traceroute.aspx

 

 

Tracing route to 86.150.49.122 [86.150.49.122]...

hop

rtt

rtt

rtt

 

ip address

fully qualified domain name

1

1

1

1

 

70.84.211.97

61.d3.5446.static.theplanet.com

2

1

0

0

 

70.87.254.1

po101.dsr01.dllstx5.networklayer.com

3

1

1

1

 

70.85.127.105

po51.dsr01.dllstx3.networklayer.com

4

0

0

0

 

70.87.253.85

e8-3.ibr03.dllstx3.networklayer.com

5

0

0

0

 

209.66.99.89

209.66.99.89.available.above.net

6

1

0

0

 

64.125.27.73

xe-0-1-0.cr1.dfw2.us.above.net

7

1

0

0

 

64.125.30.78

xe-1-0-0.cr2.dfw2.us.above.net

8

6

6

6

 

64.125.31.122

xe-4-2-0.cr2.iah1.us.above.net

9

33

57

34

 

64.125.28.49

xe-2-1-0.cr2.dca2.us.above.net

10

106

133

107

 

64.125.24.42

xe-4-1-0.mpr1.lhr3.uk.above.net

11

106

107

106

 

64.125.28.38

so-1-0-0.mpr1.lhr2.uk.above.net

12

107

108

109

 

64.125.27.150

xe-1-1-0.mpr1.lhr1.uk.above.net

13

116

107

107

 

195.66.224.69

linx1.ukcore.bt.net

14

112

112

111

 

62.6.200.102

core2-gig0-10-0-4.ilford.ukcore.bt.net

15

184

140

109

 

109.159.249.14

acc1-10gige-0-7-0-3.l-far.21cn-ipp.bt.net

16

109

109

110

 

109.159.249.85

 

17

109

109

109

 

213.120.176.177

 

18

110

109

110

 

213.120.176.21

 

19

131

168

*

 

213.120.177.9

 

20

*

*

*

 

 

 

21

*

*

*

 

 

 

22

*

*

*

 

 

 

23

*

*

*

 

 

 

Trace aborted

-- end --

0 Ratings
2 REPLIES 2
Highlighted
Geoff93
Recognised Expert
1,371 Views
Message 2 of 3

Re: Can anyone interpret this trace for me please

At which point do your outbound trace and inbound trace cross? That might give a clue as to how far from your public Ip address the inbound trace is failing.
0 Ratings
yy
Beginner
1,350 Views
Message 3 of 3

Re: Can anyone interpret this trace for me please

 Here is my outbound tracert. I guess that hop 2 is my local exchange. There is no direct match between the IPs outbound and inbound. Hop 5 and 6 on this trace below are within 1 digit of hop 10 and hop 9 respectively of the first of the reverse traces above. I'm not an expert but guess this means they are likely to be co-located? And not my local exchange unless it takes 5 hops to get out of my exchange onto the BT infrastructure.

 

 

traceroute to 199.217.10.36 (199.217.10.36), 64 hops max, 52 byte packets

 1  api (192.168.1.254)  0.896 ms  0.635 ms  0.633 ms

 2  217.32.145.136 (217.32.145.136)  22.803 ms  24.074 ms  25.768 ms

 3  217.32.145.206 (217.32.145.206)  25.868 ms  25.140 ms  24.855 ms

 4  213.120.177.10 (213.120.177.10)  23.579 ms  23.575 ms  23.913 ms

 5  213.120.176.22 (213.120.176.22)  23.895 ms  24.465 ms  23.703 ms

 6  213.120.176.178 (213.120.176.178)  24.890 ms  23.638 ms  24.422 ms

 7  acc1-10gige-0-7-0-5.l-far.21cn-ipp.bt.net (109.159.249.86)  23.800 ms

    acc1-10gige-0-2-0-6.l-far.21cn-ipp.bt.net (109.159.249.101)  24.836 ms

    acc1-10gige-0-1-0-5.l-far.21cn-ipp.bt.net (109.159.249.82)  24.035 ms

 8  core1-te0-1-0-0.ealing.ukcore.bt.net (109.159.249.21)  26.865 ms

    core2-te0-1-0-0.ilford.ukcore.bt.net (109.159.249.23)  28.352 ms

    core1-te0-15-0-2.ealing.ukcore.bt.net (109.159.249.17)  27.069 ms

 9  core1-xe1-1-0.redbus.ukcore.bt.net (62.6.200.101)  24.961 ms

    core1-xe0-0-0.redbus.ukcore.bt.net (62.6.200.73)  26.039 ms  25.040 ms

10  ge-2-1-0.mpr1.lhr2.uk.above.net (195.66.224.76)  27.001 ms  26.359 ms  26.868 ms

11  ge-3-0-0.mpr1.lhr2.uk.above.net (64.125.28.126)  25.717 ms  39.982 ms  26.313 ms

12  so-0-1-0.mpr1.dca2.us.above.net (64.125.27.57)  99.724 ms  98.703 ms  99.029 ms

13  xe-0-3-0.cr1.dca2.us.above.net (64.125.29.17)  99.676 ms  98.223 ms  99.004 ms

14  xe-0-2-0.cr1.iah1.us.above.net (64.125.25.114)  126.086 ms  125.555 ms  125.492 ms

15  xe-1-3-0.cr1.lax112.us.above.net (64.125.26.122)  157.246 ms  157.818 ms  157.267 ms

16  xe-0-2-0.cr1.sjc2.us.above.net (64.125.26.26)  166.464 ms  165.509 ms  165.713 ms

17  xe-1-0-0.cr2.sjc2.us.above.net (64.125.30.138)  164.870 ms  165.932 ms  172.025 ms

18  xe-0-1-0.er2.sjc2.us.above.net (64.125.28.21)  165.686 ms  165.177 ms  165.077 ms

19  209.249.49.10.available.above.net (209.249.49.10)  165.920 ms  166.861 ms  165.738 ms

20  ip10-178.esignal.com (199.217.10.178)  167.362 ms  166.201 ms  167.331 ms

21  ip10-140.esignal.com (199.217.10.140)  166.171 ms  165.839 ms  165.510 ms

22  * * *

23  ip225-4.esignal.com (216.23.225.4)  167.897 ms *  167.373 ms

 

 

0 Ratings