![]() |
Re: Network problems Tonight ?
I'm experiancing some bad lagging issues myself... for instance, Some IRC server's im connecting to, I keep constantly getting disconnected from (Connection reset by peer) Where as there's probably only 1 i'm able to keep connected to...
Playing games is also another issue, I keep getting disconnected from servers... It's only started happening about 2 nights ago, I just thought it was NTL doing something the first night, but now it's just continued to play up... I'm from Derby, (cpc3-stap5-4-0*.nott) (DE7*) I've got a fairly good download speed (Approx 360kb/s +)... and Ping's seem to be fine, Appart from a few IRC servers which are pinging up to 1sec sometimes |
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 ? |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
lol my speed test no uploads no other downloads
http://i3.photobucket.com/albums/y97...esGG/Snap1.jpg with and without cosham proxys 50k from guildford proxy still not a happy speed from guru3d.com http://i3.photobucket.com/albums/y97...esGG/Snap3.jpg thats happy speed my tracert tracert www.froopter.com Tracing route to www.froopter.com [66.98.246.48] over a maximum of 30 hops: 1 8 ms 6 ms 5 ms 10.75.48.1 2 6 ms 18 ms 7 ms cosh-t2cam1-b-v109.inet.ntl.com [80.3.162.145] 3 13 ms 6 ms 7 ms cosh-t2core-b-ge-wan61.inet.ntl.com [80.3.161.13 3] 4 7 ms 9 ms 9 ms gfd-bb-b-so-210-0.inet.ntl.com [62.253.188.253] 5 7 ms 7 ms 8 ms gfd-bb-a-ae0-0.inet.ntl.com [213.105.172.5] 6 9 ms 9 ms 9 ms tele-ic-1-so-110-0.inet.ntl.com [62.253.185.78] 7 282 ms 266 ms 262 ms 212.250.14.62 8 370 ms 369 ms 363 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0 .46] 9 * * * Request timed out. 10 377 ms 353 ms 343 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.6 2] 11 402 ms 415 ms 391 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3 3] 12 415 ms 412 ms 401 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.1 05] 13 418 ms 419 ms 409 ms g0-1.na21.b015619-0.iah01.atlas.cogentco.com [66 .28.64.62] 14 397 ms 405 ms 409 ms everyones_internet_2.demarc.cogentco.com [38.112 .25.158] 15 399 ms 397 ms 416 ms gphou-66-98-241-27.ev1.net [66.98.241.27] 16 407 ms 407 ms 416 ms gphou-66-98-241-125.ev1.net [66.98.241.125] 17 411 ms 406 ms 412 ms srv1.froopter.com [66.98.246.48] Trace complete. |
Re: Network problems Tonight ?
This is only going to get worse as 10mb and higher comes in and people get a lot more savvy to the speeds they should be getting for their money.
I'm not saying I should get 10mb from a single connection, but I certainly should get more than 25k though my web browser :) |
Re: Network problems Tonight ?
The old Cogent<>ntl problem is back I guess.
Permanent work is being done to sort this but will take a little while as it involves new fibre and peering connection, this should be sorted in fairly rapid time. Also by the way that hop you said that apparently belonged to ntl doesn't it's just using an IP from an ntl range, it actually is a Cogent box :p: People aren't going to be getting 10Mbit or anywhere close to it a lot of the time from a lot of sites, going to be amusing people complaining like crazy about it though ;) Infact already sorted (for now!): 8 12 ms 11 ms 13 ms tele-ic-1-so-110-0.inet.ntl.com [62.253.185.78] 9 18 ms 16 ms 17 ms 212.250.14.62 |
Re: Network problems Tonight ?
nott-cache5 attempt after ignition fix
http://www.chrysalisnet.org/ntl/nott5a.jpg max 240kB/sec avg 230kB/sec apart from flaky start looks good. So far no browsing issues on nott5 proxy. I have 12 ntl proxies in my proxy list which I cycle through including 2 other nott proxies and this is the only one that has had no issues during use O_O |
Re: Network problems Tonight ?
Quote:
Quote:
Froopter.com gives me 374k currently through Poplar, yesterday it gave me about 25k through Poplar and about 370k thru Baguley, this happens almost every day recently, and the same with my other server on a totally different network (Telia) - presumably because the proxies take different routes. I never had this inconsistency when I used Freeserve, (when they had proxies) nor do I get it now with AOL proxies on their service, every day its roughly the same (Good). I'm not naive enough to think that NTL will get rid of the proxies, all I would like is for them to work consistently (at good speeds !), so that I don't have to waste time changing to get decent speeds on different sites all the time. The NTL network seems to be pretty good here, as I've said before - non proxies connections are extremely good, gaming is great, but these proxies are pretty awful at present. Yesterday for example on 3dgamers.com(Savvis network) Default Poplar gave me about 100k a sec Baguley gave about 370k a sec ....and this is by no means unusual. I think I've made my point, and someone from NTL is listening at last (maybe) so I'll shut up now until I have some news or updates to pass on. |
Re: Network problems Tonight ?
What bamuses me is ignition and other NTL staff have not stated the reason and logic as to why they wont remove the proxies from service, even for a temporary period. He just stated a few posts ago there is a permanent fix coming into place for this one problem, (make no mistake there are dozens more) so he acknowledges the problem.
The frustration here is I have 2 choices in maxthon and IE. 1 - use the nott5 proxy or my squid proxy for good browsing, but suffer from missing images due to IE not handling specified proxes very well. 2 - dont specify a proxy so IE loads all images good but then suffer from transperent proxy issues having to hit refresh various times and not been able to use some sites. IanUK with AOL using proxies I see justification for them since they have an unmetered services, with NTL they have caps which are in the 1st stage now of becoming hard caps so they are in effect already limiting traffic and cutting their traffic costs, this should remove the need to have proxy server's since we have a traffic allocation to use as we please. Ignition your solution to the cogent issue also bemuses me, we keep hearing NTL have a outstanding internal network at low utilisation blah blah, so the internal network kicks ass good, but now we hear the peering is not so great eh? possible external traffic congestion issues going on is this the main driving force behind the policy on the proxies to keep their external traffic uncongested? |
Re: Network problems Tonight ?
better speed tonight its not 100%
but avg 250kb/s better than 20k tho |
Re: Network problems Tonight ?
Quote:
Pud |
Re: Network problems Tonight ?
Quote:
its all good down south again what about you IanUK ? thx ;-)__} |
Re: Network problems Tonight ?
still full speed on this one testfile.
|
Re: Network problems Tonight ?
Yes, my Cogent server is cool now, top whack, but my Telia hosted one is still very poor.
Also today getting DNS failures on the Poplar Proxy, I see there is a seperate thread about that today as well :( If you guys get a chance please try the same file hosted on my other server, I'm currently getting about 50k max from Poplar. But 374k FTP'ing direct to my IP. AOL gives 374k Poplar Proxy seems useless again. http://69.50.131.182/radeondriver.test The tech at Natnet (where the server is) says: 'I figure that since the cache server is the last hop down the line in the run that there's something odd at NTL between you and that machine.' Trace from my server to Poplar Proxy: traceroute to 62.253.185.81 (62.253.185.81), 30 hops max, 40 byte packets 1 69-50-137-3.mach10hosting.com (69.50.137.3) 1 ms 0 ms 0 ms 2 atl-bb1-geth1-3-0-0.telia.net (213.248.90.45) 0 ms 0 ms 2 ms 3 ash-bb1-pos7-1-0-0.telia.net (213.248.80.141) 13 ms 13 ms 14 ms 4 nyk-bb1-pos7-1-0.telia.net (213.248.80.70) 21 ms 19 ms 20 ms 5 ldn-bb1-pos7-1-0.telia.net (213.248.65.89) 89 ms 90 ms 90 ms 6 ldn-b2-pos9-0.telia.net (213.248.74.2) 91 ms 90 ms 89 ms 7 ntl-110030-ldn-b2.c.telia.net (213.248.75.90) 89 ms 88 ms 88 ms 8 bre-bb-b-so-510-0.inet.ntl.com (62.253.188.122) 89 ms 88 ms 145 ms 9 bre-bb-a-ae0-0.inet.ntl.com (213.105.172.86) 90 ms 90 ms 90 ms 10 win-bb-b-so-600-0.inet.ntl.com (62.253.185.198) 93 ms 93 ms 93 ms 11 pop-bb-a-so-000-0.inet.ntl.com (62.253.185.201) 95 ms 94 ms 95 ms 12 pop-bb-b-so-430-0.inet.ntl.com (62.253.185.81) 91 ms 91 ms 100 ms Seems fine to my untrained eye, but speeds are terrible :( Trace from my server to my IP: traceroute to 81.98.7.221 (81.98.7.221), 30 hops max, 40 byte packets 1 69-50-137-3.mach10hosting.com (69.50.137.3) 0 ms 0 ms 0 ms 2 e01.atl.fe1-2.wvfiber.net (63.223.8.181) 1 ms 1 ms 1 ms 3 pos1-6-1.ash-b0-00.wvfiber.net (63.223.0.246) 17 ms 16 ms 16 ms 4 a00.ash.pos0-0.wvfiber.net (63.223.24.14) 16 ms 16 ms 16 ms 5 e01.ash.fe1-1.wvfiber.net (63.223.24.34) 16 ms 16 ms 16 ms 6 ge-4-3-1.mpr2.iad10.us.above.net (64.125.12.189) 14 ms 14 ms 14 ms 7 so-4-0-0.mpr2.iad2.us.above.net (64.125.30.122) 15 ms 15 ms 15 ms 8 so-0-0-0.mpr1.iad2.us.above.net (64.125.28.25) 15 ms 15 ms 15 ms 9 so-4-0-0.mpr2.iad1.us.above.net (64.125.29.133) 15 ms 16 ms 15 ms 10 so-1-0-0.cr2.dca2.us.above.net (64.125.28.129) 15 ms 15 ms 15 ms 11 so-6-0-0.cr2.lhr3.uk.above.net (64.125.27.166) 100 ms 100 ms 100 ms 12 pop-bb-b-so-330-0.inet.ntl.com (208.185.188.42) 89 ms 89 ms 89 ms 13 popl-t2core-b-pos31.inet.ntl.com (62.253.185.70) 92 ms 93 ms 92 ms 14 wapk-t2cam1-b-ge-wan34.inet.ntl.com (62.255.81.174) 92 ms 91 ms 99 ms 15 ubr07seve-ge02.inet.ntl.com (80.1.170.186) 92 ms 92 ms 92 ms 16 * * Diiferent Route and speed is great. Seems sadly familar... |
Re: Network problems Tonight ?
nott5
peak 92kB/sec avg 36kB/sec squid (germany based) peak 240kB/sec avg 232kB/sec as you have already tested direct speeds this will be another case of it would be fine if the proxy was turned off. |
| All times are GMT. The time now is 12:30. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum