wake up no internet BUT read for more info

[mirdragon]

Quote:Tracing route to cpu-world.com [67.227.202.84]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 5 ms 5 ms 5 ms 217.32.143.224
3 7 ms 5 ms 4 ms 217.32.143.254
4 7 ms 8 ms 7 ms 213.120.181.26
5 8 ms 7 ms 7 ms 217.41.169.35
6 9 ms 8 ms 9 ms 217.41.169.107
7 9 ms 8 ms 9 ms acc1-10GigE-10-2-0.sf.21cn-ipp.bt.net [109.159.251.74]
8 17 ms 23 ms 23 ms core1-te0-4-0-2.ealing.ukcore.bt.net [109.159.251.1]
9 12 ms 12 ms 12 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.65.122]
10 14 ms 14 ms 13 ms t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
11 12 ms 12 ms 12 ms 166-49-211-38.eu.bt.net [166.49.211.38]
12 107 ms 107 ms 106 ms xe-1-0-0.chi12.ip4.tinet.net [89.149.187.90]
13 107 ms 107 ms 106 ms giglinx-gw.ip4.tinet.net [173.241.129.86]
14 112 ms 112 ms 112 ms lw-dc2-core4-te9-1.rtr.liquidweb.com [209.59.157.226]
15 117 ms 115 ms 113 ms lw-dc2-core4-ge2-16.rtr.liquidweb.com [209.59.157.110]
16 112 ms 116 ms 115 ms lw-dc2-sec3-dist5-po2.rtr.liquidweb.com [209.59.157.120]
17 116 ms 116 ms 114 ms 67.227.202.84

Trace complete.

I've just performed tracert from BT connection and as you can see the minute you hit xe-1-0-0.chi12.ip4.tinet.net you get a problem, so not an issue with ASK4 in that sense

But overall you can see a huge difference in response times

traceroute to bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 5 ms 5 ms 4 ms 217.32.143.224
3 5 ms 5 ms 5 ms 217.32.143.254
4 8 ms 7 ms 7 ms 213.120.181.18
5 6 ms 6 ms 6 ms 217.41.169.35
6 7 ms 7 ms 17 ms 217.41.169.107
7 7 ms 8 ms 7 ms acc1-10GigE-11-2-0.sf.21cn-ipp.bt.net [109.159.251.78]
8 19 ms 23 ms 24 ms core2-te0-4-0-2.ilford.ukcore.bt.net [109.159.251.3]
9 13 ms 13 ms 13 ms peer2-xe2-1-0.telehouse.ukcore.bt.net [109.159.254.142]
10 14 ms 14 ms 14 ms 194.74.65.42
11 * * * Request timed out.
12 15 ms 15 ms 15 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 14 ms 14 ms 14 ms 132.185.255.134
14 13 ms 13 ms 13 ms 212.58.241.131

Trace complete.

[Jimmy06]

(28-02-2012 08:33 PM)mirdragon Wrote:  

Quote:Tracing route to cpu-world.com [67.227.202.84]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 5 ms 5 ms 5 ms 217.32.143.224
3 7 ms 5 ms 4 ms 217.32.143.254
4 7 ms 8 ms 7 ms 213.120.181.26
5 8 ms 7 ms 7 ms 217.41.169.35
6 9 ms 8 ms 9 ms 217.41.169.107
7 9 ms 8 ms 9 ms acc1-10GigE-10-2-0.sf.21cn-ipp.bt.net [109.159.251.74]
8 17 ms 23 ms 23 ms core1-te0-4-0-2.ealing.ukcore.bt.net [109.159.251.1]
9 12 ms 12 ms 12 ms core1-pos5-0-0.telehouse.ukcore.bt.net [194.74.65.122]
10 14 ms 14 ms 13 ms t2as1-tge1-4.uk-lon1.eu.bt.net [166.49.211.141]
11 12 ms 12 ms 12 ms 166-49-211-38.eu.bt.net [166.49.211.38]
12 107 ms 107 ms 106 ms xe-1-0-0.chi12.ip4.tinet.net [89.149.187.90]
13 107 ms 107 ms 106 ms giglinx-gw.ip4.tinet.net [173.241.129.86]
14 112 ms 112 ms 112 ms lw-dc2-core4-te9-1.rtr.liquidweb.com [209.59.157.226]
15 117 ms 115 ms 113 ms lw-dc2-core4-ge2-16.rtr.liquidweb.com [209.59.157.110]
16 112 ms 116 ms 115 ms lw-dc2-sec3-dist5-po2.rtr.liquidweb.com [209.59.157.120]
17 116 ms 116 ms 114 ms 67.227.202.84

Trace complete.

I've just performed tracert from BT connection and as you can see the minute you hit xe-1-0-0.chi12.ip4.tinet.net you get a problem, so not an issue with ASK4 in that sense

But overall you can see a huge difference in response times

traceroute to bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 5 ms 5 ms 4 ms 217.32.143.224
3 5 ms 5 ms 5 ms 217.32.143.254
4 8 ms 7 ms 7 ms 213.120.181.18
5 6 ms 6 ms 6 ms 217.41.169.35
6 7 ms 7 ms 17 ms 217.41.169.107
7 7 ms 8 ms 7 ms acc1-10GigE-11-2-0.sf.21cn-ipp.bt.net [109.159.251.78]
8 19 ms 23 ms 24 ms core2-te0-4-0-2.ilford.ukcore.bt.net [109.159.251.3]
9 13 ms 13 ms 13 ms peer2-xe2-1-0.telehouse.ukcore.bt.net [109.159.254.142]
10 14 ms 14 ms 14 ms 194.74.65.42
11 * * * Request timed out.
12 15 ms 15 ms 15 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 14 ms 14 ms 14 ms 132.185.255.134
14 13 ms 13 ms 13 ms 212.58.241.131

Trace complete.

Hop 12 is in america