Quote:
Originally Posted by Jefferson T
Maybe you could try using port 80 or 23 for your giganews, just in case.
|
Nah see above I also tried the Giganews (HTTP based) speedtest.
I think more likely it's down to asymmetrical routing and problems along the route, or likely capacity issues on the route as I tried it just after the end of the STM period when people are likely to kick off their downloads. Downside of limiting for part of the day, it just moves the congestion period.
C:\>tracert news-europe.giganews.com
Tracing route to news-europe.giganews.com [216.196.109.144]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 12 ms 11 ms 8 ms 10.183.64.1
3 10 ms 10 ms 9 ms osr01mort-v11.network.virginmedia.net [62.30.60.1]
4 11 ms 12 ms 10 ms osr01croy-tenge73.network.virginmedia.net [62.30.242.41]
5 10 ms 9 ms 12 ms bre-bb-a-ge-300-0.network.virginmedia.net [195.182.178.82]
6 12 ms 13 ms 15 ms nth-bb-b-so-310-0.network.virginmedia.net [212.43.162.218]
7 16 ms 14 ms 14 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]
8 20 ms 23 ms 23 ms tge8-1.fr3.lon.llnw.net [87.248.208.129]
9 21 ms 25 ms 20 ms tge7-2.fr3.ams.llnw.net [69.28.171.93]
10 29 ms 20 ms 20 ms ve5.fr4.ams.llnw.net [69.28.172.114]
11 21 ms 20 ms 21 ms giganews.ve210.fr4.ams.llnw.net [87.248.196.6]
12 22 ms * 147 ms 216-196-108-133.ams.giganews.com [216.196.108.133]
Return path:
1 216-196-110-3.ams.giganews.com (216.196.110.3) 0 ms 0 ms 0 ms
2 216-196-108-134.ams.giganews.com (216.196.108.134) 0 ms 0 ms 0 ms
3 amst-ic-1.inet.ntl.com (195.69.144.40) 0 ms 0 ms 0 ms
4 pop-bb-a-as0-0.network.virginmedia.net (213.105.175.5) 10 ms 11 ms 10 ms
5 pop-bb-b-ae0-0.network.virginmedia.net (213.105.174.230) 10 ms 10 ms 11 ms MPLS Label=103680 CoS=0 TTL=0 S=1
6 osr02croy-tenge82.network.virginmedia.net (195.182.178.85) 10 ms 14 ms 10 ms
7 osr01mort-tenge81.network.virginmedia.net (62.30.242.58) 10 ms 10 ms 10 ms MPLS Label=1475 CoS=0 TTL=0 S=1