Cable Forum - View Single Post

IanUK · 26-08-2005, 15:21

traceroute to nott-cache-5.server.ntli.net (62.254.0.30), 30 hops max, 38 byte packets
1 66.98.246.1 (66.98.246.1) 0.623 ms 0.434 ms 0.604 ms
2 gphou-66-98-241-4.ev1.net (66.98.241.4) 0.676 ms 0.580 ms 0.529 ms
3 gphou-66-98-240-10.ev1.net (66.98.240.10) 0.680 ms 0.740 ms 0.781 ms
4 g0-3.na21.b015619-0.iah01.atlas.cogentco.com (38.112.25.21) 0.974 ms 1.194 ms 1.120 ms
5 g0-1.core01.iah01.atlas.cogentco.com (66.28.64.61) 2.452 ms 1.857 ms 1.271 ms
6 p13-0.core01.mci01.atlas.cogentco.com (66.28.4.106) 15.723 ms 16.340 ms 16.484 ms
7 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 29.100 ms 27.776 ms 27.328 ms
8 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 27.191 ms 27.109 ms 27.156 ms
9 p14-0.core01.bos01.atlas.cogentco.com (66.28.4.109) 66.230 ms 48.040 ms 47.878 ms
10 p3-0.core01.lon02.atlas.cogentco.com (130.117.0.45) 118.825 ms 119.625 ms 119.032 ms
11 tele-ic-1-ge-001-217.inet.ntl.com (212.250.14.61) 411.446 ms 407.205 ms 402.039 ms
12 pop-bb-b-so-430-0.inet.ntl.com (62.253.185.81) 401.492 ms 412.766 ms 411.700 ms
13 pop-bb-a-ae0-0.inet.ntl.com (213.105.172.78) 412.092 ms 404.017 ms 391.128 ms
14 nth-bb-b-so-400-0.inet.ntl.com (213.105.172.13) 395.859 ms 405.876 ms 416.889 ms
15 nott-t2core-b-pos31.inet.ntl.com (62.253.185.38) 414.475 ms 415.153 ms 415.975 ms
16 nott-cache-5.server.ntli.net (62.254.0.30) 409.078 ms 393.103 ms 393.575 ms

Still bad to that proxy.

I think the bad Cogent connection is probably a seperate issue though, although it still needs to be fixed (again)

Don't NTL monitor this kind of thing ?

It looks like each area of the countries proxies choose the best routes (ie: Poplar is currently going via cogent to my server, whereas Baguley is going via Abovenet) - which is fine in theory I guess, but means that, like now, some areas of the country get awful connections, while the others don't.

It also explains why a lot of people think we are just whining, because their proxy is taking a different route and is ok.

Surely it would give better service to choose the best routes for *everyone* and not for us the 'end users' to have to manually fart about trying to get proper speeds nearly every day to a lot of sites that we visit ?

26-08-2005, 15:21	#122
IanUK Inactive Join Date: Feb 2004 Posts: 693	Re: Network problems Tonight ? traceroute to nott-cache-5.server.ntli.net (62.254.0.30), 30 hops max, 38 byte packets 1 66.98.246.1 (66.98.246.1) 0.623 ms 0.434 ms 0.604 ms 2 gphou-66-98-241-4.ev1.net (66.98.241.4) 0.676 ms 0.580 ms 0.529 ms 3 gphou-66-98-240-10.ev1.net (66.98.240.10) 0.680 ms 0.740 ms 0.781 ms 4 g0-3.na21.b015619-0.iah01.atlas.cogentco.com (38.112.25.21) 0.974 ms 1.194 ms 1.120 ms 5 g0-1.core01.iah01.atlas.cogentco.com (66.28.64.61) 2.452 ms 1.857 ms 1.271 ms 6 p13-0.core01.mci01.atlas.cogentco.com (66.28.4.106) 15.723 ms 16.340 ms 16.484 ms 7 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 29.100 ms 27.776 ms 27.328 ms 8 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 27.191 ms 27.109 ms 27.156 ms 9 p14-0.core01.bos01.atlas.cogentco.com (66.28.4.109) 66.230 ms 48.040 ms 47.878 ms 10 p3-0.core01.lon02.atlas.cogentco.com (130.117.0.45) 118.825 ms 119.625 ms 119.032 ms 11 tele-ic-1-ge-001-217.inet.ntl.com (212.250.14.61) 411.446 ms 407.205 ms 402.039 ms 12 pop-bb-b-so-430-0.inet.ntl.com (62.253.185.81) 401.492 ms 412.766 ms 411.700 ms 13 pop-bb-a-ae0-0.inet.ntl.com (213.105.172.78) 412.092 ms 404.017 ms 391.128 ms 14 nth-bb-b-so-400-0.inet.ntl.com (213.105.172.13) 395.859 ms 405.876 ms 416.889 ms 15 nott-t2core-b-pos31.inet.ntl.com (62.253.185.38) 414.475 ms 415.153 ms 415.975 ms 16 nott-cache-5.server.ntli.net (62.254.0.30) 409.078 ms 393.103 ms 393.575 ms Still bad to that proxy. I think the bad Cogent connection is probably a seperate issue though, although it still needs to be fixed (again) Don't NTL monitor this kind of thing ? It looks like each area of the countries proxies choose the best routes (ie: Poplar is currently going via cogent to my server, whereas Baguley is going via Abovenet) - which is fine in theory I guess, but means that, like now, some areas of the country get awful connections, while the others don't. It also explains why a lot of people think we are just whining, because their proxy is taking a different route and is ok. Surely it would give better service to choose the best routes for everyone and not for us the 'end users' to have to manually fart about trying to get proper speeds nearly every day to a lot of sites that we visit ?