![]() |
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... |
Re: Network problems Tonight ?
Bad again now at 11:14 this morning.
Target Name: www.froopter.com IP: 66.98.246.48 Date/Time: 26/08/2005 11:13:21 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 7 ms 9 ms popl-t2core-a-ge-wan64.inet.ntl.com [62.255.81.65] 5 7 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 9 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 8 247 ms 252 ms [212.250.14.62] 9 320 ms 323 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46] 10 341 ms 345 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110] 11 340 ms 344 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62] 12 353 ms 355 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33] 13 366 ms 370 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.105] 14 369 ms 369 ms g0-2.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.66] 15 369 ms 372 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158] 16 114 ms 114 ms gphou-66-98-241-27.ev1.net [66.98.241.27] 17 114 ms 114 ms gphou-66-98-241-125.ev1.net [66.98.241.125] 18 115 ms 114 ms srv1.froopter.com [66.98.246.48] I reported this exact fault in this thread ages ago, it was supposed to be fixed :( So that two faults now they are ignoring, the Proxies and the network, very poor... |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
According to Ignition it is NTL, he posted this earlier in this thread:
Quote:
|
Re: Network problems Tonight ?
I stand corrected....
|
Re: Network problems Tonight ?
Just thought I'd add my little bit.
I've had network probs for last 10 days. Some sites download fine others are crawling... and my speed check on adslguide.org fluctuates between 90k and 190k every time I run it. Currently on 2mb connection with NTL. I'm down in the South of UK Pudders |
Re: Network problems Tonight ?
I'm in Essex, I've finally had a reply from someone at NTL, I'll let you all know what the outcome is !
Maybe these proxies will finally get sorted....(or not) |
Re: Network problems Tonight ?
Quote:
Pud |
Re: Network problems Tonight ?
im in portsmouth and its been crap speed since end of july
before that had no problem anytime of the day or night i could load at 360k but now lucky to get 120k :td: you kno what itll be theyll put a laptop to your line text some sites they use and say "theres no fault on your line sir" "maybe its your pc or some software " but i DO HOPE you have better luck than we had !!!!!! |
Re: Network problems Tonight ?
for what its worth, Reading (RG10) is really lagging just now ..
Mark |
Re: Network problems Tonight ?
Quote:
Pud |
Re: Network problems Tonight ?
Quote:
You are using the 'cosh-cache-5.server.ntli.net' proxy server. This is an ntl Proxy Server in the Cosham area. so yeah this is my default proxy |
Re: Network problems Tonight ?
I am still using this nott-cache 5 proxy from last night although not been using it very long, so far no timeouts.
what is very unusual that on this proxy dnsreport works. |
Re: Network problems Tonight ?
Quote:
PUd |
Re: Network problems Tonight ?
Ok done some tests on
http://www.froopter.com/radeondriver.test Ianuk if you can do a traceroute from your server to nott-cache5.server.ntli.net please. the nott-cache5 still has the slowness for downloads so the guy who gave it me claiming no problems is either lying to make it look like the problem isnt there or downloads no files from offshore servers or is satisfied with lower speeds or has the 1mbit package. download speed graph for nott5-cache. Peak 160kB/sec avg 86kB/sec http://www.chrysalisnet.org/ntl/nott5.jpg download speed graph for squid, located in germany (further distance) Peak 236kB/sec avg 218kB/sec http://www.chrysalisnet.org/ntl/squid.jpg colc-cache2 speed graph. Peak 128kB (been generous) avg 51kB/sec http://www.chrysalisnet.org/ntl/colc2.jpg finally my default proxy speed graph. Peak 160kB/sec avg 92kB/sec http://www.chrysalisnet.org/ntl/default.jpg graphs taken with netlimiter showing my total traffic My connection was otherwise idle. __________________ Quote:
|
Re: Network problems Tonight ?
I'm currently mucking about with the list of NTL proxies to see if I can see which ones are any good for improving download speeds. When I change them in the LAN settings do I need to put any exceptions box?
Can you just run by the exact way to change a proxy with what boxes should be checked/unchecked. I agree though.. the Nott 5 proxy was quicker for browsing but no improvement on download speed. Pud |
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. |
Re: Network problems Tonight ?
Code:
08/27/05 22:25:35 Fast traceroute http://69.50.131.182 |
Re: Network problems Tonight ?
Yeah traces look fine, its weird, but I just tried the download and still only get about 50k max from Poplar Proxy, I get 355k from AOL....
Hopefully someone from NTL will get back to me this coming week with a reason and fix :) BTW: homealone: You might want to not make the link clickable above, that site is not suitable for this forum I think, thats why I always used the ip and not url ;) |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
can you be more specific where on telia this is?
I have telia server's located in germany which are fine even on these proxies, and its 100ms from those so doesnt seem to be a neighboring country. |
Re: Network problems Tonight ?
I thought this had been locked?
Update. All my customers in the Woking area appear to be surfing to their satisfaction. Thanks for putting up with my moaning. |
Re: Network problems Tonight ?
Quote:
USA, Telia in Europe is fine for me too. __________________ Quote:
|
Re: Network problems Tonight ?
Oh fantastic.
When I lock a thread it tends to stay locked. Thanks again to this forum. NTL problems increase my work but if it is not a pc problem then I dont get paid. My choice. I would not touch them following the occasion three years ago when my faher in law died and they transferred the account to my address even though we are not connected on cable and charged me for three months for the service. They still owe me 42 pence. And the life reducing esperience of "hanging on" |
Re: Network problems Tonight ?
Quote:
If you have a problem with the moderation on this site, please contact a member of the Team via Private Message. |
Re: Network problems Tonight ?
I think its good it stayed unlocked because ignition's fix for the cogent issue is temporary and I for one would like to know when they have the permanent fix in place (new fibre).
|
Re: Network problems Tonight ?
nott5 bailed out on me for a couple of minutes, it did well for a proxy just about 2 days with no browsing problems.
|
Re: Network problems Tonight ?
still loading at 370k it looks like its ok down here in the south
:tu: |
Re: Network problems Tonight ?
Speeds dropped again today, looks like Cogent is going again :(
Target Name: www.froopter.com IP: 66.98.246.48 Date/Time: 29/08/2005 15:50:38 2 6 ms 13 ms [10.82.176.1] 3 7 ms 7 ms wapk-t2cam1-a-ge-wan41-112.inet.ntl.com [80.1.170.57] 4 9 ms 7 ms popl-t2core-a-ge-wan64.inet.ntl.com [62.255.81.65] 5 7 ms 7 ms pop-bb-a-so-330-0.inet.ntl.com [213.105.174.113] 6 8 ms 8 ms pop-bb-b-ae0-0.inet.ntl.com [213.105.172.77] 7 9 ms 9 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 8 139 ms 146 ms [212.250.14.62] 9 211 ms 208 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46] 10 230 ms 225 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110] 11 228 ms 229 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62] 12 242 ms 241 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33] 13 253 ms 255 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.105] 14 253 ms 255 ms g0-2.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.66] 15 254 ms 255 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158] 16 134 ms 132 ms gphou-66-98-241-27.ev1.net [66.98.241.27] 17 134 ms 134 ms gphou-66-98-241-125.ev1.net [66.98.241.125] 18 133 ms 132 ms srv1.froopter.com [66.98.246.48] and between 11 and 40k from my Telia server There was mention of new fibre for the Cogent problem, is there going to be new fibre for the Telia USA problem as well, if anything my speeds are even slower with that provider :( AOL is managing 374k from both currently.. *sigh* |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
Got a brand new cogent issue, ntl to staminus going over cogent.
staminus have 3 backbones in their network mix, abovenet, cogent and nrs, they tried to depreference cogent and nrs but I am told ntl are making it go over cogent, there is a jump to 380ms which is usually 160ms on abovenet and 200ms on nrs. Trace below, target ip private. but range is 72.20.x 1 24 ms 8 ms 7 ms 10.8.143.254 2 9 ms 8 ms 12 ms leic-t2cam1-a-ge914.inet.ntl.com [82.3.35.149] 3 7 ms 7 ms 7 ms leic-t2core-a-ge-220-0.inet.ntl.com [82.3.33.10] 4 8 ms 10 ms 9 ms lee-bb-a-so-220-0.inet.ntl.com [62.253.188.110] 5 15 ms 14 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238] 6 33 ms 16 ms 15 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 7 201 ms 200 ms 197 ms 212.250.14.62 8 272 ms 267 ms 270 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0 .46] 9 295 ms 323 ms 295 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.11 0] 10 298 ms 332 ms 299 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.6 2] 11 312 ms 312 ms 313 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3 3] 12 330 ms 338 ms 333 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.1 05] 13 369 ms 360 ms 388 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6 ] 14 354 ms 357 ms 362 ms p4-0.core01.lax01.atlas.cogentco.com [66.28.4.77 ] 15 371 ms 377 ms 381 ms p15-0.core02.lax04.atlas.cogentco.com [154.54.1. 54] 16 378 ms 410 ms 376 ms g0-2.na21.b000899-0.lax04.atlas.cogentco.com [66 .250.8.166] 17 372 ms 365 ms 393 ms brdr02-4ge.lax1.staminus.net [72.20.0.170] 18 373 ms 364 ms 375 ms edge01-ge.lax1.staminus.net [72.20.0.1] 19 397 ms 388 ms 400 ms core02-ge1.irv1.staminus.net [72.20.0.33] 20 397 ms 386 ms 386 ms csr1-ge.irv1.staminus.net [72.20.0.180] 21 389 ms 384 ms 390 ms xxx.xxx.org [72.20.x.x] friend who works at ntl says ntl peering congested but he hasnt got the access to fix. So I am hoping ignition can have a look thanks. |
Re: Network problems Tonight ?
Even worse now :(
Target Name: www.froopter.com IP: 66.98.246.48 Date/Time: 29/08/2005 21:03:07 2 7 ms [10.82.176.1] 3 6 ms wapk-t2cam1-a-ge-wan41-112.inet.ntl.com [80.1.170.57] 4 11 ms popl-t2core-a-ge-wan64.inet.ntl.com [62.255.81.65] 5 7 ms pop-bb-a-so-330-0.inet.ntl.com [213.105.174.113] 6 10 ms pop-bb-b-ae0-0.inet.ntl.com [213.105.172.77] 7 11 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 8 210 ms [212.250.14.62] 9 275 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46] 10 303 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110] 11 295 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62] 12 306 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33] 13 322 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.105] 14 322 ms g0-2.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.66] 15 327 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158] 16 133 ms gphou-66-98-241-27.ev1.net [66.98.241.27] 17 132 ms gphou-66-98-241-125.ev1.net [66.98.241.125] 18 139 ms srv1.froopter.com [66.98.246.48] And my test file from my other Telia USA hosted server is less than 15k now, pathetic again. As usual - direct connections, or AOL proxies bring both still in at full speed, I think its time someone from NTL did something about this :( |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
The Cogent issue is separate to the proxy issue I think, it only affects my server through the web browser because the Poplar Proxy chooses that route, direct connections go through Abovenet and don't suffer the same.
My other server is different though, traces look ok, but speeds through NTL proxies are terrible, All other ISP's seem fine, just NTL users that are having problems connecting to my server(s). Direct connections show the bandwidth is there, so its not congestion this end, it looks like NTL's peering is pretty poor, this is two networks now that are suffering, its either that or the proxies, I don't know :( I ask again, why don't NTL monitor this kind of thing ? The Cogent fix is coming we are told, and it was fixed temporarily, so why can't it be fixed temporarily again, and keep fixing it temporarily until the fibre arrives ? This has been going on for weeks now. I see yet another proxy problem thread started today as well (http://www.cableforum.co.uk/board/sh...ad.php?t=34293), thats at least one a day recently, NTL fix these things PLEASE !!!!! |
Re: Network problems Tonight ?
The cogent issue is defenitly nothing to do with the proxies, I noticed it when there was a massive pause waiting for my ssh session to respond, ssh traffic is direct and doesnt use proxies. I havent done any speed tests over ftp. This kind of thing I agree with you I expect to be monitored so I am guessing one of 2 things, ntl have waited until its full to the brim before the new fiber got laid, or these recent high speeds people have been reporting caused a surge in the utilisation.
|
Re: Network problems Tonight ?
1 Attachment(s)
Just to back up IanUK, I have no proxy set, yet when I use VisualRoute to trace the route to that site, the ping time rises at the last point in the route that's in the NTL network. According to NTL, this point is where NTL peer to Cogent.
|
Re: Network problems Tonight ?
Quote:
I agree. This stinks of bad management. The market is horribly competitive. I dont know but it seems as though they have looked at the competition and are being told to deliver the same. Bad move as far as I can see. Pipex are giving me 2 meg with no problem but they never promised it. Interesting distiction there when they agree a one meg connection and you get 2 you think "Oh Thanks". Promise ten and degrade the whole network and nobody is happy. |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
I'm guessing its cost, Cogent is well known for being a cheap provider, most 'pile em high' type internet businesses (Newshosting/Newsreader/Filefront/EV1) will have Cogent bandwidth for their High Usage situations and I'm guessing its also cheaper for NTL to route using Cogent.
None of this helps us poor customers of course :( And other ISP's seem to manage with Cogent just fine. Perhaps Telia is a cheap route as well ? might explain why it also suffers from about 12pm onwards.... In fact after more research it seems that NTL's peering is pretty poor all round, Easynews has a route selector tool that lets you choose the network that carries your bandwidth, their support forum is full of uk cable users that have very poor connections to them using virtually all of the networks, Level 3 works great for me to them, full speed, but the other providers (Qwest,LLNW,UU & ATT) are all very poor (mid 100k's) so thats another 4 providers that NTL seem to have poor speeds with. I think its looking to be network probs and not proxies...it just shows as the proxies because different proxies can take different routes...or maybe it *is* the proxies, I don't know, we can witter on for ages here talking to ourselves but we need someone from NTL to answer my Responstek as promised !! |
Re: Network problems Tonight ?
I just realised that my old news server takes the same route, its mighty strange that i used to go through the same 'mental' hop as you but could flat line 360kb/s with four threads.
That was from February for some months...something happened on ~16th June, could not get over 130kb/s even with 8 threads. They upgraded something, unrelated really and soon after I could max out with 8 threads, on occasions it was flaky between 320 and 350 but nothing to shout about. |
Re: Network problems Tonight ?
Quote:
right now the cogent problem is back to normal, but I wonder what it will be like tonight. So much of usa is turning to cogent now which is very scary since the provider is still below the standards of AT&T abovenet etc. However many providers still have it amongst a mix of providers so that does still leave the likes of NTL with a choice of route, so I am very dissapointed NTL have opted for budget over quality since they sell the "we cap you but it improves quality" so much. |
Re: Network problems Tonight ?
its back as predicted.
6 18 ms 17 ms 20 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 7 243 ms 221 ms 216 ms 212.250.14.62 8 285 ms 294 ms 290 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0 .46] __________________ ok staminus have had me run some tests and have done something their end to help force change the route, it hasnt kicked in yet and wont kick in if ntl have cogent forced. test #1 to abovenet ntl to above handoff - 60ms - poor - possible congestion 5 15 ms 14 ms 17 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238] 6 63 ms 76 ms 63 ms so-4-0-0.cr2.lhr3.uk.above.net [208.185.188.41] 7 167 ms 111 ms 112 ms so-7-0-0.cr2.lga1.us.above.net [64.125.31.182] test #2 ntl to nrs handoff - 90ms - very poor likely congestion 8 19 ms 19 ms 17 ms tele-ic-2-so-110-0.inet.ntl.com [62.253.185.74] 9 86 ms 99 ms 123 ms cr02.ldn01.pccwbtn.net [195.66.224.167] test #3 ntl to cogent - very poor - 200ms - confirmed congestion 6 16 ms 20 ms 15 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 7 195 ms 201 ms 201 ms 212.250.14.62 8 289 ms 284 ms 286 ms p10-0.core01.bos01.atlas.cogentco.com [130.117. .46] looks like with all the ubr upgrades going on ntl forgot about their peering, no wonder they keeping the proxies enabled, external traffic is pretty clogged. |
Re: Network problems Tonight ?
problems easing a bit.
6 17 ms 15 ms 23 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 7 162 ms 164 ms 169 ms 212.250.14.62 8 217 ms 221 ms 216 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0 abovenet looks clear now 5 15 ms 14 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238] 6 20 ms 21 ms 66 ms so-4-0-0.cr2.lhr3.uk.above.net [208.185.188.41] |
Re: Network problems Tonight ?
at 1am cogent looks normal.
6 34 ms 19 ms 25 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 7 22 ms 18 ms 59 ms 212.250.14.62 8 90 ms 90 ms 91 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0 .46] |
Re: Network problems Tonight ?
Looks like its Cogent/Telia/Abovenet & PCCWBTN thats proven to be getting congested then
Just to keep everyone up to date - I've had two replies to my Responsetek form, and am now awaiting a call from the broadband department. I'm not sure why they have to call me when all the info is in this thread and affects other people than me, but thats fine if thats how they want to do it. I've been told I'll be contacted by this Friday, I'll post here when I get more details. |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
Quote:
__________________ All of the problem points are in the UK, thats why there is a problem with the peering it seems :( Abovenet UK HOP: 6 63 ms 76 ms 63 ms so-4-0-0.cr2.lhr3.uk.above.net [208.185.188.41] Cogent UK Hop: 7 195 ms 201 ms 201 ms 212.250.14.62 PCCWBTN UK Hop: 9 86 ms 99 ms 123 ms cr02.ldn01.pccwbtn.net [195.66.224.167] All far higher than they should be at peak times (and often off peak in the case of Cogent) |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
You are wrong or ignition is wrong then :)
Ignition told us the hop you are talking about (212.250.14.62) is in the UK, in fact currently it pings about 9, so its impossible to be in the USA, so I think ignition is right. |
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
The problem is before(or as) it leaves NTL, once it gets to the USA its already delayed, clearly shown in our traces recently at the *first* largest hop in Stuart c's trace and ours.
The USA hops are always going to be larger :) |
Re: Network problems Tonight ?
Okay, nevermind - I only looked at Stuart's image and read the previous hop as 14, it's actually 141. I'll go and book my appointment at specsavers now ... :blush:
|
Re: Network problems Tonight ?
Having to use Baguley proxy tonight as Poplar won't resolve this site :(
Edit: As seen below looks like for once it wasn't a Poplar Proxy fault. Back to low speeds on Cogent. Both sites still slow as usual. :( |
Re: Network problems Tonight ?
Site been off for 1 1/2 hours tonight.
|
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
Quote:
http://www.cableforum.info/board/showthread.php?t=212 |
Re: Network problems Tonight ?
hello whose fault this time :rolleyes:
what ^^^^ said |
Re: Network problems Tonight ?
My connection has been up and down like a brides nightie tonight :erm: :rolleyes:
|
Re: Network problems Tonight ?
Quote:
|
Re: Network problems Tonight ?
Quote:
200ms to london is NOT normal :( __________________ Had some connectivity issues to kpn last night it affected noone else, but traceroutes looked normal. Tonights congestion tests. 11.40pm cogent 6 18 ms 17 ms 20 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 7 121 ms 124 ms 137 ms 212.250.14.62 8 191 ms 195 ms 195 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0 .46] abovenet 5 15 ms 15 ms 18 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238] 6 21 ms 23 ms 20 ms so-4-0-0.cr2.lhr3.uk.above.net [208.185.188.41] nrs - pccwtbn 8 17 ms 14 ms 29 ms tele-ic-2-so-110-0.inet.ntl.com [62.253.185.74] 9 19 ms 16 ms 19 ms cr02.ldn01.pccwbtn.net [195.66.224.167] 10 195 ms 190 ms 193 ms 63.218.51.46 abovenet and nrs both looking ok, although its late evening, unfortenatly although staminus went out their way to depreference cogent my traffic is still going through it from ntl. Cogent itself is congested quite heavily but less then last night. |
Re: Network problems Tonight ?
Hi, Ok its all way over my head, but have a look in forums? There is a lot of posts about limited or no conectivity, slow speeds, lag, poor upload speeds and dropping conections, Now ive had all of them in the last frew days, and iam down in the BN area, i get it at 0600am and ive just had a bad one at 1810hrs. What is going on?:dozey: ps sorrey about the poor english:dunce:
|
Re: Network problems Tonight ?
Just my nightly post, both sites still slow.
getting boring now.... |
Re: Network problems Tonight ?
cogent this morning (4am) took its own **** and routed traffic from uk-france-amsterdam then hitting usa at 360ms this wasn't directly ntl's fault but one would have expected them to not be routing traffic thru cogent if possible but of course they did.
Staminus have disabled cogent FULLY for my server at their datacentre because NTL wasnt responding to the cogent been depreferenced, the staminus owner who knows a fair bit about bgp protocol has come to the conclusion that NTL are simply using cogent no matter what preference its set to at the other end which does explain why its congestion gets so bad. The issue here is he cannot keep me at this configuration permanently and I will be back onto the bgp mix within a few days, my contact at NTL says he will look at it but says I am wrong about NTL forcing the cogent route but I cant think of another reason why the cogent route is ALWAYS used even when going through france and holland en route. __________________ currently cogent heavily congested, nrs normal, abovenet normal. |
Re: Network problems Tonight ?
My server tonight:
Target Name: www.froopter.com IP: 66.98.246.48 Date/Time: 02/09/2005 21:38:02 2 7 ms [10.82.176.1] 3 7 ms wapk-t2cam1-a-ge-wan41-112.inet.ntl.com [80.1.170.57] 4 7 ms popl-t2core-a-ge-wan64.inet.ntl.com [62.255.81.65] 5 8 ms pop-bb-a-so-330-0.inet.ntl.com [213.105.174.113] 6 8 ms pop-bb-b-ae0-0.inet.ntl.com [213.105.172.77] 7 10 ms tele-ic-1-so-010-0.inet.ntl.com [62.253.185.82] 8 229 ms [212.250.14.62] 9 301 ms p10-0.core01.bos01.atlas.cogentco.com [130.117.0.46] 10 323 ms p5-0.core01.ord01.atlas.cogentco.com [66.28.4.110] 11 322 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62] 12 333 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.33] 13 345 ms p12-0.core01.iah01.atlas.cogentco.com [66.28.4.105] 14 347 ms g0-2.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.66] 15 346 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158] 16 114 ms gphou-66-98-241-27.ev1.net [66.98.241.27] 17 116 ms gphou-66-98-241-125.ev1.net [66.98.241.125] 18 115 ms srv1.froopter.com [66.98.246.48] 50k speeds - again :( My other server is fine by direct connection, but the proxies give less than 50k also...again. For those that care - despite being contacted by Executive Office staff at NTL (twice) and being promised a call by 9pm tonight at the latest, that still NO ONE has contacted me regarding any of these issues. - its been 3 weeks now since my official complaint. If you have proxy issues then no one at NTL cares, they have clearly shown this I think. I'm not posting in this thread any longer,unless I get an answer or something drastic changes, as I'm clearly just wasting my time. I'd ask that the team don't close it just yet as I have written Richard Bourne at NTL an email telling him exactly what I think of his companies 'service' and pointed him here, I doubt he'll bother answering or looking here, as they have been pretty useless so far - but I'd like to at least give him the option. |
Re: Network problems Tonight ?
I would like this thread to stay open so if any of us gets information we can post updates, I will stop posting nightly reports as by now we all know whats going on.
|
Re: Network problems Tonight ?
I would allso, keep it open.
|
Re: Network problems Tonight ?
Just an update, NTL contacted me tonight, and we went through my problems, they are going to test my two server downloads at various times tomorrow to see if they get the same slowdowns that I do.
I think we may be nearing the end of this mammoth task :) Oh, and Betanews.com is now working on the Poplar Proxies ;) cheers Ian |
Re: Network problems Tonight ?
so you mentioned about having to cycle proxies as well?
|
Re: Network problems Tonight ?
OK, had a follow up call tonight, we have narrowed the problem down regarding the slow speeds to my server to the fact that only one of the Poplar proxies is giving me full speeds, we tested each one individually, and all but one were giving very poor speeds, this is being escalated and I have been asked to give it one week and I should see the difference.
As far as I'm concerned this thread can be closed now, or moved, whichever the mods want to do, the problem of the proxies (speedwise at least) in my area is now hopefully being looked into. cheers Ian |
Re: Network problems Tonight ?
I'll close it for the time being so i can have a good look at what has been said... there may be some unresolved issues that need attention, but there are so many different issues in one place that if the thread is reopened it will be cleaned up first :)
|
| All times are GMT. The time now is 08:04. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum