Newshosting connections explained
Short answer
Newshosting allows up to 100 connections at once, the most of the big Highwinds brands; Easynews and UsenetServer allow 60. Most home setups hit full speed with 20 to 40 in SABnzbd, so only go higher on a fast line or when you're far from the servers. The limit is per account, which means every device you run shares the same 100.
Set Newshosting to 20 to 30 connections in SABnzbd to start with, and only add more while your download speed keeps going up. You're allowed 100, but you'll rarely need all of them. The limit covers your whole account, so a NAS and a laptop downloading at the same time are drawing from one shared pool.
Newshosting's 100 against other providers
| Provider | Backbone | Max connections | Price on the longest term |
|---|---|---|---|
| Newshosting | Highwinds | 100 | $12.95/mo on 12 months |
| UsenetServer | Highwinds | 60 | $7.95/mo on 12 months |
| Easynews | Highwinds | 60 | $9.99/mo on 12 months |
| Giganews | Certida | 100 | $8.33/mo on 12 months |
| Eweka | Eweka | 50 | €6.99/mo on 15 months |
| NewsDemon | UsenetExpress | 50 | $30 per 15 months after intro |
Checked 22 Oct 2026. Newshosting, UsenetServer and Easynews all serve the same stored Highwinds files, which makes the higher connection limit one of the few things that actually sets Newshosting apart.
Finding the right number in four steps
- Set Newshosting to 20 connections on news.newshosting.com, port 563 with SSL.
- Download a big file and note the speed SABnzbd settles at, ignoring the first minute.
- Add 10 connections and try again. Stop once the speed stops rising.
- Settle on a number slightly above where the speed levelled off, so brief slowdowns on single connections don't show up.
A gigabit line keeps gaining speed for longer than a 100 Mbit line before it levels off. At that speed other bottlenecks appear, such as disk speed and unpacking, which our page on Usenet for gigabit connections covers. Distance plays a part as well. If you live far from the US and European server sites, for example in Australia, you'll usually need more connections, because each one spends longer waiting for an answer.
Sharing 100 connections around the house
| Device | Connections | Reason |
|---|---|---|
| NAS running SABnzbd for Sonarr and Radarr | 50 | Does most of the downloading |
| Desktop with SABnzbd for manual grabs | 30 | Only used now and then |
| Laptop newsreader | 10 | Browsing headers needs only a few |
| Spare | 10 | Keeps you under the limit if a client reconnects |
Go over 100 in total and Newshosting turns away the extra logins, which SABnzbd reports as connection errors. Downloads carry on over the connections that did get in, but the errors clutter the log and can hide real problems.
Problems more connections won't solve
Connections change your speed, not which articles exist. A job that fails with missing articles on 20 connections will fail in exactly the same way on 100. What you need then is a backup server on another backbone, often called a fill server. It has its own connection limit, so none of its connections count against your Newshosting 100. Usenet connections explained has more background.
FAQ
- Do SSL connections count the same as plain ones?
- Yes. Use SSL on port 563 for every connection, because it makes no difference to the limit.
- Is the limit per device or per account?
- Per account. Every device that logs in with the same details shares the 100.
- Will 100 connections overload a small NAS?
- It can. Each connection takes a little CPU for SSL, so a low-power box may max out before your internet connection does.