Slow Downloads - GigaNews - Page 2

grubbymitts · 09-04-2006, 20:14

with Newshosting try port 9000, 8000 or 3128 when you get slowdowns. I just got full speed off those ports.

Zee · 09-04-2006, 22:30

I'm having the same problem with BitTorrent (uTorrent) usually i get 200-220KB/s im now struggling to get 15KB/s ... the last few days its been like this

basil · 10-04-2006, 00:11

i think its a problem with NTL...just wait a couple of days for it be fixed

Chrysalis · 10-04-2006, 02:42

if you have to have 10 concurrent connections to hit 10meg speeds then something is congested, they cap speed per thread or it is a very big rtt.

basil · 10-04-2006, 12:21

i think speeds are coming back to normal..

Taf · 10-04-2006, 12:38

ntl's own news servers have been start-stopping all morning....

Widescreen · 10-04-2006, 13:14

Yea GigaNews seems to be back to normal aswell as of 3 this morning.

Lets hope it stays that way

Bart39 · 10-04-2006, 20:56

Quote:

Originally Posted by grubbymitts

with Newshosting try port 9000, 8000 or 3128 when you get slowdowns. I just got full speed off those ports.

yep worked for me, set port to 9000 and went back up to full speed (was avg 3 mb)

zorab · 11-04-2006, 13:04

I've been having and continue to have the same problem that folks are describing here but it affects almost all my browsing and downloading.

I'm on a 10mb connection, for example, previous downloads from Easynews were maxing out my 10Mb connection, now they barely reach 1mb and in the evening speeds are no better than a dialup modem!

Curiously, when I do the speedtest at adslguide.org all my connections speeds check out just fine, 10mb down and 500kb up.

I'm in the East London area - can anyone shed any light on whats happening? Is it something to do with this traffic shaping malarkey?!

Cheers

darius · 11-04-2006, 19:26

I use Easynews and have been getting slow downloads. A tracert reveals ths:
Tracing route to easynews.com [140.99.99.90]
over a maximum of 30 hops:
1 20 ms 7 ms 19 ms 10.249.0.1
2 16 ms 9 ms 7 ms nott-t2cam1-b-v124.inet.ntl.com [80.4.46.137]
3 7 ms 7 ms 8 ms nott-t2core-b-ge-wan72.inet.ntl.com [80.1.79.189
]
4 9 ms 10 ms 9 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
5 14 ms 12 ms 11 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
6 14 ms 13 ms 11 ms 195.50.91.69
7 11 ms 11 ms 11 ms ae-0-56.bbr2.London1.Level3.net [4.68.116.162]
8 116 ms 119 ms 116 ms ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109]
9 139 ms 135 ms 136 ms as-1-0.mp2.Phoenix1.Level3.net [64.159.1.122]
10 135 ms 138 ms 137 ms ge-7-2.hsa1.Phoenix1.Level3.net [4.68.98.36]
11 162 ms * 163 ms eth-2-37-1g.core-03.phx1.puregig.net [64.154.128
.14]
12 166 ms 163 ms 169 ms www.easynews.com [140.99.99.90]
Trace complete.
Note number 8

A reverse trace from Easynews shows this:

HOSTLOSSRCVDSENTBESTAVGWORSTge1-8-1000m.sw1.easynews.com0%10100.346.8850.11e-2-11-1000m.core-03.phx1.puregig.net0%10100.282.2718.10ge2-13.fr1.phx1.llnw.net0%10100.679.8390.96agg1-16-1.ar1.phx1.llnw.net0%10101.2110.2852.97so1-5-1.ar1.dal.llnw.net0%101028.4029.3631.27so1-5-2.ar1.ord.llnw.net0%101052.9053.4155.35so1-5-2.ar1.lga.llnw.net10%91078.5091.38130.70so1-5-1.ar1.lon.llnw.net10%910152.36153.11154.56ag1-21.fr1.lon.llnw.net0%1010151.94155.45171.86195.66. 224.2560%410221.41291.59351.63bre-bb-b-as0-0.inet.ntl.com40%610144.49144.94145.87bre-bb-a-ge-000-0.inet.ntl.com30%710144.88148.22162.12gfd-bb-b-so-700-0.inet.ntl.com40%610146.30151.54176.61nth-bb-a-so-000-0.inet.ntl.com20%810148.30148.78149.75nth-bb-b-ae0-0.inet.ntl.com50%510148.28159.93184.40nott-t2core-b-pos51.inet.ntl.com10%910149.84157.15194.80nott-cache-13.server.ntli.net30%710149.74167.39270.37
The router most likely responsible for your slow downloads in owned by llnw.net.

195.66.224.25 seems to be the link, trying to find info on this points to a server in London. Easynews say it is owned by NTL. I understand that NTL are doing a lot of upgrading there. Has any one else done a tracert? Does any one have the expertise to explain this more clearly to me?

---------- Post added at 18:26 ---------- Previous post was at 18:18 ----------

Sorry about the last part of that post, my inexperience showing through. Talking to Easynews, they say the most likely cause is an overloaded router in London. My download has now dropped to 7.33 KB/sec Yikes!!!

IanUK · 11-04-2006, 19:29

LLNW in my experience is a terrible route to NTL, use Level 3 or Qwest or AT&T from Easynews route change page, and make sure you use port81 or secure port 81.

darkone338 · 11-04-2006, 23:20

Quote:

I use Easynews and have been getting slow downloads. A tracert reveals ths:
Tracing route to easynews.com [140.99.99.90]
over a maximum of 30 hops:
1 20 ms 7 ms 19 ms 10.249.0.1
2 16 ms 9 ms 7 ms nott-t2cam1-b-v124.inet.ntl.com [80.4.46.137]
3 7 ms 7 ms 8 ms nott-t2core-b-ge-wan72.inet.ntl.com [80.1.79.189
]
4 9 ms 10 ms 9 ms nth-bb-b-so-200-0.inet.ntl.com [62.253.185.37]
5 14 ms 12 ms 11 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
6 14 ms 13 ms 11 ms 195.50.91.69
7 11 ms 11 ms 11 ms ae-0-56.bbr2.London1.Level3.net [4.68.116.162]
8 116 ms 119 ms 116 ms ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109]
9 139 ms 135 ms 136 ms as-1-0.mp2.Phoenix1.Level3.net [64.159.1.122]
10 135 ms 138 ms 137 ms ge-7-2.hsa1.Phoenix1.Level3.net [4.68.98.36]
11 162 ms * 163 ms eth-2-37-1g.core-03.phx1.puregig.net [64.154.128
.14]
12 166 ms 163 ms 169 ms www.easynews.com [140.99.99.90]
Trace complete.
Note number 8

The jump between 7 and 8 is fine. This is the transatlantic crossing. Most ISPs quote around 90ms for the east coast and around 120ms to the west coast. As I cant decypher the last part, I cant really help.. Have you tried the other ports? From their www page

Quote:

proxy.news.easynews.com listens on ports 22, 23, 53, 80, 110 and 443 to allow you to bypass firewalls or rate limits on port 119

James Henry · 12-04-2006, 06:45

*Snip*

darius - this thread is about Giganews really, but in your case your slow speeds are caused by an overloaded peering link between llnw.net and ntl - I believe Easynews allow you to change your routing, and strongly suggest you do this.

Second to all, there's no traffic shaping action going on there it looks like congestion and poor routing.

Most news servers offer options to change routing paths, have a play and see if you can resolve by changing the route you are taking.

Also remember that a traceroute can take a completely different route from the server to you, and you to the server so if using these as proof of a fault always good to get the reverse one as well if you can helps to locate the fault.

Just to reiterate this appears to be congested peering as changing routing resolves the issue, there is no evidence of traffic shaping or throttling in the evidence provided

This thread is hard to read, could a mod please break down the offending massive line in post 25?

darius · 12-04-2006, 09:04

Sorry about the messed up post, I've never posted on a forum before. However, thanks for the advice. I will experiment with the re-routing and see what happens.

James Henry · 12-04-2006, 09:27

Quote:

Originally Posted by darius

Sorry about the messed up post, I've never posted on a forum before. However, thanks for the advice. I will experiment with the re-routing and see what happens.

Not a problem at all mate, try it should work around the problem link and sort the issue.

Ta.