Roadrunner and/or Newshosting Speed Issue
Posted: January 11th, 2012, 1:38 am
Hello everyone!
I know this isn't an issue with SABnzbd, but I'm hoping someone here will have some insight as to what I can do to improve my speeds, if it's possible.
I'm using Roadrunner (not lite or turbo, just regular) and according to multiple speed tests, I get 20-30Mbps (or 2.5-3.75MB/s if I understand correctly). In SABnzbd, my downloads will start out for a second or two at 3MB/s and then it will decrease and settle at a consistent 1.2MB/s.
I spoke with Newshosting and after providing them with my ping and traceroute, they told me the issue is with Roadrunner because they send me through multiple servers so there is nothing that can be done on Newshosting's end (I believe that's what Newshosting said. The correspondence was a few months ago and unfortunately I did not keep the email). I have not spoken with Roadrunner because I don't know how I would bring up the fact that I am downloading large files via usenet and I am receiving slower than anticipated speeds.
Here is a ping and traceroute if that helps at all:
I know this isn't an issue with SABnzbd, but I'm hoping someone here will have some insight as to what I can do to improve my speeds, if it's possible.
I'm using Roadrunner (not lite or turbo, just regular) and according to multiple speed tests, I get 20-30Mbps (or 2.5-3.75MB/s if I understand correctly). In SABnzbd, my downloads will start out for a second or two at 3MB/s and then it will decrease and settle at a consistent 1.2MB/s.
I spoke with Newshosting and after providing them with my ping and traceroute, they told me the issue is with Roadrunner because they send me through multiple servers so there is nothing that can be done on Newshosting's end (I believe that's what Newshosting said. The correspondence was a few months ago and unfortunately I did not keep the email). I have not spoken with Roadrunner because I don't know how I would bring up the fact that I am downloading large files via usenet and I am receiving slower than anticipated speeds.
Here is a ping and traceroute if that helps at all:
Code: Select all
ping newshosting.com
Pinging newshosting.com [74.209.130.181] with 32 bytes of data:
Reply from 74.209.130.181: bytes=32 time=51ms TTL=50
Reply from 74.209.130.181: bytes=32 time=49ms TTL=50
Reply from 74.209.130.181: bytes=32 time=49ms TTL=50
Reply from 74.209.130.181: bytes=32 time=48ms TTL=50
Ping statistics for 74.209.130.181:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 51ms, Average = 49msCode: Select all
tracert newshosting.com
Tracing route to newshosting.com [74.209.130.181]
over a maximum of 30 hops:
1 13 ms 10 ms 10 ms 10.108.48.1
2 11 ms 11 ms 11 ms rdc-24-93-12-31.wny.northeast.rr.com [24.93.12.3
1]
3 13 ms 16 ms 15 ms rdc-72-230-153-4.wny.northeast.rr.com [72.230.15
3.4]
4 18 ms 14 ms 14 ms rdc-72-230-153-243.wny.northeast.rr.com [72.230.
153.243]
5 30 ms 27 ms 29 ms 107.14.19.28
6 45 ms 44 ms 46 ms ae-4-0.cr0.nyc20.tbone.rr.com [66.109.6.24]
7 46 ms 46 ms 44 ms ae-0-0.cr0.nyc30.tbone.rr.com [66.109.6.26]
8 51 ms 49 ms 52 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
9 51 ms 54 ms 52 ms 107.14.19.135
10 60 ms 51 ms 50 ms 3-3.r1.dc.hwng.net [69.16.190.113]
11 51 ms 61 ms 48 ms ve913.ar3.dc.hwng.net [209.197.1.34]
12 51 ms 48 ms 50 ms unknown.hwng.net [74.209.130.181]
Trace complete.