Re: Network problems Tonight ?
 

Ian I have said it numerous times now, they can do something about it. They can stop haveing them cumpolsary. But its a decision someone wont budge on. The cash they save I would guess is neglegible since browsers now days by default cache images. Browsing is so much faster and smoother on a broadband connection with no proxies, but so many of us here have got used to this. People go into robot mode when they specify a new proxy every day.

Re: Network problems Tonight ?
 

I see yet another proxy thread started today as well, this is surely a pretty big problem now, The team here have helped me a lot by trying to get someone at NTL to answer my Responsetek form and I thank them for it, and I shall continue to try and get an answer, but it looks like NTL know they are useless and don't care - so much for customer service (or indeed providing what we are paying for in those areas affected)

The NTL network when NOT using the proxies (FTP/NNTP/POP3) seems to be very good to me, when I don't use proxies I get very good speeds indeed, but web browsing takes several clicks on links to get anywhere and then it just crawls along, or gives an out of date page - or in a lot of cases refuses to load a site at all or until refreshed about 5 times.

All I can suggest at this stage is that everyone affected by this problem raise a Responsetek form, if we all do it then maybe they'll listen (although by the number of proxy problems reported on this forum over the last few years and still nothing is done I doubt it)

ho hum

Re: Network problems Tonight ?
 

this confuses me, i've never changed a proxy and never experienced a bad service, all my IE links work quickly as they should, why do people keep going on about NTL proxies, my service has been fine from ever since BB started years ago and i use it everyday?. Is it a Northern thing

Re: Network problems Tonight ?
 

I honestly think some people over hype these things, if it was a great a problem, there would of have been something done about it.

I only have to use a proxy to get to whatever site very rarely. I think the peeps who complain should state what proxy it is they are going through, if its *that* bad then I'm sure others who can try their proxy will agree.

Re: Network problems Tonight ?
 

Sorry but FFS.

I wouldn't be bothering to post here for fun.

How much plainer can I make it?

There are problems and NTL are useless at fixing them.

A customer signed up and was connected last week. I had to go back yesterday and was greatly relieved and, frankly, surprised to find it all working fine. This customer lives within 500 yards of two others who are having horrendous problems which I can't get fixed.

So yes some customers are currently having a good experience and well done for NTL for those. Getting some of them working fine idicates that the problems can be fixed.

Should be simple enough. Very basic but try looking at a happy customers setting on the same node and an unhappy one and figure out what is set up differently.

We are not over hyping this, we are incredibly frustrated.

Re: Network problems Tonight ?
 

Can I ask what type of sites you tend to visit? and where were you when the cableforum broke down under the ntl proxies over the last few days, I wonder if some people are soft and ignore problems like slow down of pages timeouts etc. Or it could be your proxy is one of few that work well and if so good for you.

There are actually 2 new threads I noticed, one is in the computers and IT forum where the user thought it was his pc, mods didnt move it for what reason they felt suitable.

I am in Leicester, east midlands. Colchester whereever that is their proxies suffer the same problems.
__________________

dnsreport has promoted me from a basic error to this"WARNING: You are using a web proxy that is currently being abused by malware. Please go here for more details. The web proxy IP is 82.3.32.76"

Re: Network problems Tonight ?
 

Lucky you, nope not a Northern thing, I'm in London - in fact the Northern proxies I try are better than Poplar.

LOL, I thought that too, but now that I've been trying since 12 August to get someone/anyone from NTL to respond through their official channels, I think not. Add to that the fact that *we* had to tell NTL when they brought in 3 meg that their proxies were wrongly configured for USA sites and you'll forgive me for not really agreeing with you there.

I've been quoting my proxy group all the way through this thread, I've been posting traces, I keep track of downloads to my servers at different times of the day, and some proxies work fine - think yourself lucky that you are using some that work ok, but please don't patronise those of us that are CLEARLY having problems and being ignored.

Maybe we are wrong, maybe its something all of us suffering have installed on our pc's, maybe we all use weird sites that no one else uses - maybe its space monkeys - unfortunately we won't know because no one from NTL will talk to me, it seems from reading proxy posts going back on this board for years that whenever proxies are mentioned that NTL clams up, and this seems to be the case again :(

I'm glad you can surf ok, I'm happy for you.
I shall console myself with that thought as I struggle to open my account in EBuyer for the 4th time....

Re: Network problems Tonight ?
 

Yeah I thought the same thing as you posted it, its contradicting when the saying is NTL will act upon it if people open their mouth's but the feedback channels I imagine are data going into oblivion.

When I spoke to simon duffy's PA the problem I had then was she hadnt the foggiest what I was on about as she had no technical knowledge, so whilst I got someone listening I had to explain to the best of my ability what was wrong.

Another problem is one day proxy A works well then goes bad after few hours so I switch to proxy B that works well for 10 minutes then I switch to proxy C that works well for 30 mins, I go back to proxy A which is all hunky dory again, I get the feeling there are dozens of people doing the exact same thing which is why we going around in circles on the proxy cycling, and there are the sites that just dont work well at all such as ebuyer and ebay, hotmail, dnsreport.

Re: Network problems Tonight ?
 

OK, whatever, carry on complaining but if it is your proxy, then why not just change and help the situation.

Try mine, 'if they all keep failing' - nott-cache-5.server.ntli.net:8080

Re: Network problems Tonight ?
 

Do be aware that ebuyer are desparately over their sever capacity at the moment. I buy a lot of kit from them and they are horiibly slow web wise.

A victim of their own success.


Anything after 11 am forget it.

Re: Network problems Tonight ?
 

using nott-cache-5.server.ntli.net now.

well ebuyer is flawless when not using ntl proxies so I based my judgement on that.

Re: Network problems Tonight ?
 

Been having exactly the same problems here (Oldham) recently, takes longer to load static sites whilst dynamic sites time out, the problem appears to coincide with the maintenance in different areas, changing from transparent to Baguley proxy cures it immediately. The ntl homepage is one of the problem sites, I bet the advertisers could get something done if they were aware of the problem ;)

Re: Network problems Tonight ?
 

Well I dont use NTL :)

Re: Network problems Tonight ?
 

well sorry to hear of your problems but never have i had any probs with ebuyer and ebay, hotmail, dnsreport, due to NTL proxy?

if i had proxy problems that required switching every 10/30mins i think i'd move onto someone else becasue its seems clear your not getting what you paid for and NTL in your case isn't helping you or know what to do when others appear to be fine with the service and its proxy setups

Re: Network problems Tonight ?
 

Earlier in this thread I posted a link to my server and a test file, that file is now back down to 25k a sec, here is the trace right now from one of my servers to the Poplar Proxy:

traceroute to 62.253.185.81 (62.253.185.81), 30 hops max, 38 byte packets
1 66.98.246.1 (66.98.246.1) 1.897 ms 3.063 ms 0.344 ms
2 gphou-66-98-241-4.ev1.net (66.98.241.4) 0.534 ms 2.765 ms 0.561 ms
3 gphou-66-98-240-10.ev1.net (66.98.240.10) 0.575 ms 3.369 ms 0.690 ms
4 g0-3.na21.b015619-0.iah01.atlas.cogentco.com (38.112.25.21) 1.073 ms 0.950 ms 0.941 ms
5 g0-1.core01.iah01.atlas.cogentco.com (66.28.64.61) 1.326 ms 1.329 ms 1.193 ms
6 p13-0.core01.mci01.atlas.cogentco.com (66.28.4.106) 15.817 ms 16.077 ms 16.179 ms
7 p5-0.core02.ord01.atlas.cogentco.com (66.28.4.34) 38.145 ms 28.869 ms 27.800 ms
8 p15-0.core01.ord01.atlas.cogentco.com (66.28.4.61) 27.673 ms 27.508 ms 27.112 ms
9 p14-0.core01.bos01.atlas.cogentco.com (66.28.4.109) 47.807 ms 47.947 ms 51.525 ms
10 p3-0.core01.lon02.atlas.cogentco.com (130.117.0.45) 118.380 ms 118.398 ms 122.243 ms
11 tele-ic-1-ge-001-217.inet.ntl.com (212.250.14.61) 410.684 ms 370.789 ms 373.545 ms
12 pop-bb-b-so-430-0.inet.ntl.com (62.253.185.81) 390.724 ms 396.753 ms 397.536 ms

Going from my ip to my server:

Target Name: www.froopter.com
IP: 66.98.246.48
Date/Time: 25/08/2005 23:28:58
2 6 ms 6 ms [10.82.176.1]
3 7 ms 7 ms wapk-t2cam1-a-ge-wan41-112.inet.ntl.com [80.1.170.57]
4 8 ms 8 ms popl-t2core-a-ge-wan64.inet.ntl.com [62.255.81.65]
5 8 ms 8 ms pop-bb-a-so-330-0.inet.ntl.com [213.105.174.113]
6 8 ms 9 ms pop-bb-b-ae0-0.inet.ntl.com [213.105.172.77]
7 9 ms 10 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82]
8 262 ms 257 ms [212.250.14.62]
9 325 ms 327 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46]
10 345 ms 348 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110]
11 343 ms 347 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62]
12 356 ms 359 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33]
13 370 ms 372 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.105]
14 371 ms 375 ms g0-2.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.66]
15 371 ms 378 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158]
16 115 ms 119 ms gphou-66-98-241-27.ev1.net [66.98.241.27]
17 115 ms 115 ms gphou-66-98-241-125.ev1.net [66.98.241.125]
18 115 ms 116 ms srv1.froopter.com [66.98.246.48]

I thought this problem had been fixed :( :(


And now from the server to the Baguley proxy:

traceroute to bagu-cache-4.server.ntli.net (80.5.160.7), 30 hops max, 38 byte packets
1 66.98.246.1 (66.98.246.1) 0.505 ms 0.401 ms 0.338 ms
2 gphou-66-98-241-4.ev1.net (66.98.241.4) 0.718 ms 0.495 ms 0.576 ms
3 gphou-66-98-240-9.ev1.net (66.98.240.9) 0.705 ms 0.555 ms 1.093 ms
4 ge-6-0-0.mpr1.iah1.us.above.net (216.200.251.165) 1.733 ms 1.242 ms 1.315 ms
5 so-0-0-0.mpr2.iah1.us.above.net (64.125.31.62) 1.849 ms 2.939 ms 1.794 ms
MPLS Label=258928 CoS=6 TTL=1 S=0
6 so-5-0-0.mpr1.atl6.us.above.net (64.125.29.65) 14.282 ms 14.063 ms 14.191 ms
MPLS Label=261008 CoS=6 TTL=1 S=0
7 so-0-0-0.mpr2.atl6.us.above.net (64.125.27.50) 14.515 ms 14.245 ms 14.186 ms
MPLS Label=245184 CoS=6 TTL=1 S=0
8 so-3-1-0.cr1.dca2.us.above.net (64.125.29.38) 25.766 ms 25.364 ms 25.374 ms
MPLS Label=376672 CoS=6 TTL=1 S=0
9 so-6-0-0.cr1.lhr3.uk.above.net (64.125.31.185) 97.144 ms 97.057 ms 97.127 ms
MPLS Label=100160 CoS=6 TTL=1 S=0
10 pos1-0.mpr1.lhr1.uk.above.net (208.184.231.173) 117.535 ms 186.817 ms 276.362 ms
MPLS Label=425 CoS=6 TTL=1 S=0
11 pos4-0.mpr2.lhr1.uk.above.net (208.185.156.14) 97.012 ms 96.932 ms 97.317 ms
12 gfd-bb-a-so-000-0.inet.ntl.com (208.185.188.30) 109.294 ms 110.372 ms 109.414 ms
13 pop-bb-b-so-000-0.inet.ntl.com (213.105.172.138) 109.301 ms 109.182 ms 109.313 ms
14 lee-bb-a-so-700-0.inet.ntl.com (62.253.185.237) 114.963 ms 114.928 ms 114.937 ms
15 lee-bb-b-ae0-0.inet.ntl.com (62.253.187.186) 114.639 ms 150.554 ms 114.698 ms
16 bagu-t2core-b-pos71.inet.ntl.com (213.105.174.74) 115.907 ms 116.867 ms 115.818 ms
17 bagu-cache-4.server.ntli.net (80.5.160.7) 118.051 ms 115.763 ms 116.059 ms

Different route, and its fine, maybe the problem isn't the proxy itself, but the routes Poplar takes, its more proof that there is a problem, but no one is listening :(

It seems everyone should be using Bageley, perhaps thats the answer, make all the proxies take the same routes as Bageley, everyone likes that !
__________________

My other server is the same, takes Telia to NTL using Poplar Proxy and Abovenet using Baguley, it seems we have a clue......


But is anyone listening...