Usenet - NZB Speeds on Voyager?

Forums › Voyager › Usenet - NZB Speeds on Voyager?

Jiriteach

1116 posts

Uber Geek

ID Verified

Lifetime subscriber

#315273 28-Jun-2024 08:21

I have a Voyager max fibre link as a second connection and been trying a few things out.
Very impressed with speeds apart from Usenet. No problems with wider speeds.

On my Spark connection - I easily see 110-115mb/sec.
On my Voyager connection - looks to be hard limited to 60mb/sec.

What Usenet - NZB speeds to others experiencing?

-- opinions expressed by me are solely my own. ie - personal

gehenna

8460 posts

Uber Geek

Moderator

Trusted

Lifetime subscriber

#3254070 28-Jun-2024 12:32

How many concurrent connections are set? Tinker with those. Is it unpacking as it downloads or after it finishes? If it's while downloading, is it to the same drive as the download or another drive?

Jiriteach

1116 posts

Uber Geek

ID Verified

Lifetime subscriber

#3254106 28-Jun-2024 14:33

gehenna: How many concurrent connections are set? Tinker with those. Is it unpacking as it downloads or after it finishes? If it's while downloading, is it to the same drive as the download or another drive?

100

Unpacking after it downloads

If I switch to Spark - I'll see the huge speed increase so intrested to know why. All other speeds with Voyager have been fine including several speedtests.

-- opinions expressed by me are solely my own. ie - personal

eluSiveNZ

188 posts

Master Geek

#3254189 28-Jun-2024 17:07

Interesting, when I was on Voyager i had the same experience, max 60MB/s.

Tried all sorts of things and gave up and just accepted it in the end.

OldGeek

876 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#3254280 28-Jun-2024 21:50

In my experience it is worth raising this through an email Voyager Support: support@voyager.nz. I have raised several issues this way and have always got a response that was good with detail and suggestions.

--

OldGeek.

Voyager referral code: https://refer.voyager.nz/6XQR2QG9Q

Jiriteach

1116 posts

Uber Geek

ID Verified

Lifetime subscriber

#3254310 29-Jun-2024 09:19

OldGeek:

In my experience it is worth raising this through an email Voyager Support: support@voyager.nz. I have raised several issues this way and have always got a response that was good with detail and suggestions.

Thanks - have flicked the team an email. Will wait to see what they say.

-- opinions expressed by me are solely my own. ie - personal

Firebirdnz

35 posts

Geek

Trusted

Voyager

#3254315 29-Jun-2024 09:39

Hey all. Sorry I'm not aware of this service. What's the IP endpoint? If you access over DNS, what does it resolve to via spark VS voyager? We don't rate limit access to any service or protocol nor do we restrict access to anything on the network. If there is a rate limit somewhere it'll be off our network. With the above information I can do some digging and ask some questions.

Regards,
~H

Jiriteach

1116 posts

Uber Geek

ID Verified

Lifetime subscriber

#3254320 29-Jun-2024 09:51

Firebirdnz: Hey all. Sorry I'm not aware of this service. What's the IP endpoint? If you access over DNS, what does it resolve to via spark VS voyager? We don't rate limit access to any service or protocol nor do we restrict access to anything on the network. If there is a rate limit somewhere it'll be off our network. With the above information I can do some digging and ask some questions.

Regards,
~H

Good to know - Thanks.

Endpoint - news.newshosting.com
Here's some traceroutes - Routes look very similar so confused why the difference in speed. Consistenly max's at 60mb/sec on Voyager and ~ 110 mb/sec on Spark. Have run several tests to confirm. Spark connects via PPPoE. Tried Voyager on both PPPoE and IPoE. Nothing else changed between the test. DNS is Cloudflare.

Via Voyager -

dummer:~ $ traceroute news.newshosting.com
traceroute to news.newshosting.com (85.12.62.251), 30 hops max, 60 byte packets

1 unifi.ui.local (192.168.178.1) 0.096 ms 0.071 ms 0.093 ms
2 lo-vprn-100.br1.wgn.vygr.net (114.23.17.255) 1.431 ms 1.331 ms 1.341 ms
3 ae-0-448.edge01.wgn.vygr.net (114.23.17.230) 1.236 ms 1.194 ms 1.133 ms
4 et-0-0-1-0.core01.wgn.vygr.net (43.240.33.78) 10.901 ms 10.957 ms 10.854 ms
5 et-0-0-1-0.edge01.cpc.vygr.net (43.240.33.89) 10.868 ms 10.850 ms 10.792 ms
6 et-0-0-0-0.core01.cpc.vygr.net (43.240.33.112) 10.644 ms 10.573 ms 10.531 ms
7 et-0-0-0-0.edge02.trg.vygr.net (43.240.33.97) 7.863 ms 8.685 ms 8.674 ms
8 et-0-0-3-0.edge01.trg.vygr.net (114.23.29.22) 9.023 ms 8.920 ms 8.872 ms
9 et-0-0-15-0.core02.mdr.vygr.net (43.240.33.46) 11.260 ms 11.329 ms 10.581 ms
10 et-0-0-3-0.edge01.mdr.vygr.net (43.240.33.43) 10.903 ms 10.809 ms 12.299 ms
11 ae9-143.akbr6.global-gateway.net.nz (122.56.118.157) 11.835 ms 11.631 ms 11.797 ms
12 ae7-2.akbr7.global-gateway.net.nz (122.56.119.53) 12.197 ms 11.750 ms 11.627 ms
13 * ae10-10.tkbr12.global-gateway.net.nz (202.50.232.29) 11.681 ms *
14 xe8-0-6.lebr7.global-gateway.net.nz (122.56.119.122) 136.618 ms xe7-0-1-10.lebr7.global-gateway.net.nz (202.50.232.162) 137.427 ms ae0-10.lebr8.global-gateway.net.nz (202.50.232.42) 147.777 ms
15 ae0-10.lebr8.global-gateway.net.nz (202.50.232.42) 143.030 ms 141.504 ms 140.725 ms
16 ae-12.sayonara-mikael.r25.lsanca07.us.bb.gin.ntt.net (129.250.3.179) 141.445 ms ae-8.sayonara-mikael.a03.lsanca20.us.bb.gin.ntt.net (129.250.203.45) 140.347 ms *
17 ae-12.sayonara-mikael.r25.lsanca07.us.bb.gin.ntt.net (129.250.3.179) 141.254 ms ae-5.sayonara-mikael.r25.asbnva02.us.bb.gin.ntt.net (129.250.3.188) 193.108 ms ae-12.sayonara-mikael.r25.lsanca07.us.bb.gin.ntt.net (129.250.3.179) 140.386 ms
18 ae-5.sayonara-mikael.r25.asbnva02.us.bb.gin.ntt.net (129.250.3.188) 194.110 ms ae-1.sayonara-mikael.a05.asbnva02.us.bb.gin.ntt.net (129.250.3.244) 200.304 ms 198.033 ms
19 ae-1.sayonara-mikael.a04.asbnva02.us.bb.gin.ntt.net (129.250.2.125) 202.575 ms ae-0.omicron.asbnva02.us.bb.gin.ntt.net (128.241.9.67) 193.660 ms ae-1.sayonara-mikael.a04.asbnva02.us.bb.gin.ntt.net (129.250.2.125) 189.056 ms
20 ae-1.omicron.asbnva02.us.bb.gin.ntt.net (128.241.10.89) 193.993 ms 85.12.50.77 (85.12.50.77) 191.902 ms ae-0.omicron.asbnva02.us.bb.gin.ntt.net (128.241.9.67) 193.252 ms
21 85.12.50.77 (85.12.50.77) 192.039 ms * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Via Spark -

dummer:~ $ traceroute news.newshosting.com
traceroute to news.newshosting.com (85.12.62.251), 30 hops max, 60 byte packets

1 unifi.ui.local (192.168.178.1) 0.587 ms 0.535 ms 0.508 ms
2 * * *
3 * * *
4 122.56.119.216 (122.56.119.216) 11.064 ms 11.065 ms 11.044 ms
5 ae10-10.tkbr12.global-gateway.net.nz (202.50.232.29) 11.566 ms 11.620 ms 11.673 ms
6 xe7-0-1-10.lebr7.global-gateway.net.nz (202.50.232.162) 136.955 ms 203.96.120.142 (203.96.120.142) 135.996 ms xe11-0-2.lebr7.global-gateway.net.nz (122.56.119.126) 135.767 ms
7 ae0-10.lebr8.global-gateway.net.nz (202.50.232.42) 134.704 ms 135.196 ms 135.109 ms
8 ae-8.sayonara-mikael.a03.lsanca20.us.bb.gin.ntt.net (129.250.203.45) 147.319 ms 146.879 ms 146.830 ms
9 * * ae-12.sayonara-mikael.r25.lsanca07.us.bb.gin.ntt.net (129.250.3.179) 142.353 ms
10 ae-5.sayonara-mikael.r25.asbnva02.us.bb.gin.ntt.net (129.250.3.188) 198.024 ms 202.019 ms 201.543 ms
11 ae-1.sayonara-mikael.a05.asbnva02.us.bb.gin.ntt.net (129.250.3.244) 196.184 ms 201.085 ms 197.571 ms
12 ae-0.omicron.asbnva02.us.bb.gin.ntt.net (128.241.9.67) 197.751 ms 201.948 ms 197.754 ms
13 85.12.50.79 (85.12.50.79) 191.961 ms 196.478 ms 196.095 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

-- opinions expressed by me are solely my own. ie - personal

Tradepub

Free professional, reference and technical white papers (affiliate link).

Shindig

1581 posts

Uber Geek

Trusted

#3269632 9-Aug-2024 03:52

Any other developments?

Any comment from Voyager on throttling?

The little things make the biggest difference.

jrdobbs

106 posts

Master Geek

#3269677 9-Aug-2024 09:36

Simple question, is usenet still a thing in 2024?

Jiriteach

1116 posts

Uber Geek

ID Verified

Lifetime subscriber

#3269678 9-Aug-2024 09:38

Shindig:

Any other developments?

Any comment from Voyager on throttling?

Nope - no further developments. Voyager confirmed that there isnt any throttling so not much more that one can do about it.

-- opinions expressed by me are solely my own. ie - personal

jrdobbs

106 posts

Master Geek

#3269680 9-Aug-2024 09:50

Instead of running traceroute, have you tried using mtr so you can see if you have any packet loss or slow downs in traffic along the way?

Jiriteach

1116 posts

Uber Geek

ID Verified

Lifetime subscriber

#3269764 9-Aug-2024 10:46

jrdobbs:

Instead of running traceroute, have you tried using mtr so you can see if you have any packet loss or slow downs in traffic along the way?

I did but didnt spend much more time looking into it. Seems that its upstream from Voyager that could be causing the diff'ering speeds. I've tested a few other ISP's and seem similar consistent upstream speeds to Voyager. Spark's upstream does not seem to have this issue.

Provided some answers for now which is good enough.

-- opinions expressed by me are solely my own. ie - personal