Quote:
|
Originally Posted by Nikko
80.1.79.57 seems to have woken up, pem:
|
Well hopefully someone has given it a good kicking
Quote:
|
Originally Posted by DrAwesome
Tracing route to nthellworld.co.uk [216.40.241.59]
|
Both those traces show what I said, they are both taking exactly the same route on the NTL network to the Telehouse LINX ;
2 midd-t2cam1-a-ge-wan34-103.inet.ntl.com [213.106.238.17]
3 midd-t2core-a-ge-wan61.inet.ntl.com [213.106.237.33]
4 lee-bb-a-so-130-0.inet.ntl.com [62.253.187.89]
5 pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
6 tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]
Once they leave NTL's network they are still taking the same route but then the trace on the first one stops in the middle of the Williams Communications (US) network for some reason;
First;
7 lndnuk1icx1.wcg.net [195.66.224.105]
8 nycmny2wcx2-oc12.wcg.net [64.200.87.149]
9 hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
10 * * * Request timed out.
Second;
7 lndnuk1icx1.wcg.net [195.66.224.105]
8 nycmny2wcx2-oc12.wcg.net [64.200.87.149]
9 hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
10 hrndva1wcx3.oc48.wcg.net [64.200.95.78]
11 drvlga1wcx2-pos.wcg.net [64.200.210.57]
12 drvlga1wcx1-oc48.wcg.net [64.200.127.29]
13 dllstx1wcx3-oc48.wcg.net [64.200.240.21]
14 dllstx1wcx2-oc48.wcg.net [64.200.110.73]
15 hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
16 hstntx1wce2-everyonesinternet-gige.wcg.net [65.77.93.54]
17 ivhou-207-218-223-34.ev1.net [207.218.223.34]
Having said all this, your second trace starts out badly on the first step [for which you seem to have removed the IP & name details] - this is your UBR so it may be you have a local problem. (This may have been what interrupted the first trace as well).