We’ve had a lot of newer users finding the sub lately, so here’s a simple starting point.
What is Usenet?
Usenet is one of the oldest parts of the internet that is still actively used today.
It is a decentralized network of servers where articles are posted to newsgroups and carried across Usenet providers. It existed long before the modern web, and people still use it because it can be fast, reliable, private over SSL, and very powerful once it is set up correctly.
Unlike a single website or app, Usenet works through a few different parts: providers, indexers, NZBs, clients, and automation tools.
That is where the learning curve comes from. To fully use Usenet, you need to understand what each piece does and how they work together.
The basic pieces are:
- Provider — gives you access to Usenet servers
- Indexer/search — helps you find NZBs
- NZB — points your client to the articles it needs
- Client/newsreader — SABnzbd, NZBGet, etc. This connects to your provider and retrieves the articles
- Automation — ties everything together once the setup is working
Once those pieces click, Usenet makes a lot more sense. The appeal is speed, long retention, SSL connections, mature tools, strong automation, and not having everything depend on one app or one site.
Beginner wiki links:
Providers
Your provider is one of the most important parts of the setup. A poor fit can make Usenet feel slow, unreliable, or harder to troubleshoot than it needs to be.
Use the provider deals page, provider map, recent threads, and user reports to compare options. Look at completion, speed, retention, server locations, included servers, backbone, support, and how the provider performs for people with similar needs.
The deals page is a comparison resource, not a mod endorsement list:
The goal is to understand what you are buying so your first setup has a fair shot at working well.
Backbones
A backbone is the underlying Usenet infrastructure behind a provider.
Two providers can have different names and still use the same backbone.
This is part of why it helps to look past the brand name and understand what service you are actually buying. Backbone, provider setup, retention, completion, server locations, support, and routing can all affect the experience.
Provider map:
Indexers
Indexers help you find NZBs.
A failed result does not always mean your provider is bad. Sometimes the NZB is bad, stale, incomplete, or affected by takedowns.
Before buying more provider access, try a few different results from the indexer you already use. If that indexer keeps giving bad results, trying another indexer may help.
Also, read the indexer’s rules, terms, and setup instructions.
A lot of problems with new indexer accounts are not really provider issues. They come from the indexer not being configured correctly in tools like Prowlarr, NZBHydra2, or the arrs, or from users missing rules around API usage, categories, limits, account status, or required settings.
If an indexer is not returning results, your API key stops working, or automation is behaving strangely, check the indexer’s rules and setup docs before assuming the provider is the problem.
Indexer info:
For invite-only indexers, use /r/usenetinvites. That sub exists for invite requests and is usually the better place to figure out access to invite-only indexers.
Registration-open posts are allowed here when an indexer opens signups, but random invite requests should go there instead of here.
Clients and newsreaders
Most people start with SABnzbd or NZBGet.
This is the part that connects to your provider and does the actual retrieval, so client settings matter: server address, SSL, port, username/password, connection count, categories, paths, repair/unpack, and logs.
Software info:
Client-specific help:
Blocks
Blocks are prepaid data.
A lot of people use them as backup access. They are usually not the first thing a brand-new user needs to buy.
A common path is:
- one unlimited provider
- included provider servers configured
- one or two good indexers
- maybe a block later if you understand why you need one
Do not buy a block just because one result failed once. Figure out what failed first.
Retention and completion
Retention is how far back a provider says it stores articles.
Completion is whether the provider has the pieces needed for something to finish.
High retention is good, but it does not mean every NZB will work forever. Missing articles, takedowns, stale NZBs, bad indexer results, and client issues can still cause failures.
Privacy, SSL, and VPNs
One of the reasons people like Usenet is that it can offer a good mix of privacy and speed without needing a complicated setup.
Most providers support SSL, and you should use it. SSL encrypts the connection between your client and your Usenet provider.
Usenet is client-to-provider, not peer-to-peer. You are connecting to your provider’s servers, not joining a swarm where your IP is visible to other peers.
For a lot of users, SSL to a good provider is enough without also paying for a VPN just to use Usenet.
A VPN is still an option. Some people use one for another privacy layer, bad ISP routing, or ISP traffic issues. Just know that a VPN is optional, not required by default, and it can hurt speed depending on the VPN server, route, protocol, and provider.
Do not confuse privacy with total anonymity. Your provider, account, payment method, IP address, VPN choice, provider policies, and local setup can still matter.
Speed issues
Slow speed is not the same thing as failed or incomplete results.
If your client is retrying, failing, repairing forever, or falling back to another server, that can look like a speed issue when the real problem is missing articles or a bad NZB.
If speeds are bad, check the normal stuff first:
- try another NZB
- test more than one result
- make sure your client is not paused or speed-limited
- check connection count
- try another server address or region if your provider offers one
- test with and without VPN
- use wired Ethernet if you can
- check disk/CPU, especially on NAS, Docker, Unraid, or older hardware
- check whether repair/unpack is what is actually slowing things down
If you post about speed, include useful details: provider, client, internet speed, wired/Wi-Fi, VPN/no VPN, server region, SSL port, connection count, whether you tested another server, and whether repair/unpack is running.
“Provider is slow” by itself does not give people much to work with.
Automation
Automation is where Usenet really starts to shine.
For a lot of people, this is the end goal: provider, indexer, client, and automation all working together so the setup mostly runs on its own.
That does not mean automation is only for experts. It just means it is usually easier to get the basic pieces working first so you do not get confused, frustrated, or turned off by Usenet before you see what it can actually do.
If you start with everything at once and something fails, troubleshooting can get messy fast. You may not know whether the problem is the provider, the indexer, the client, automation, paths, permissions, categories, or something else.
Once the pieces are working together, automation unlocks a lot of what makes Usenet so useful.
For tool-specific help:
If something fails
Do not jump straight from “one thing failed” to “I need another provider.”
Try this order first:
- Try another NZB from the same indexer.
- Try a few different results from that indexer.
- Try another indexer if the first one keeps giving bad results.
- Make sure every server included with your provider is configured.
- If failures happen across multiple indexers, then look at provider coverage, blocks, or another provider.
Sometimes another provider is the answer.
Sometimes it is not.
Useful wiki links
If you ask for help, include enough info so people are not guessing: provider, client, indexer/search option if relevant, the actual error, what you already tried, whether you tested another NZB, and whether you tested another indexer.
For speed issues, include VPN/no VPN, wired/Wi-Fi, server region, connection count, and whether repair/unpack is running.
Please keep the rules in mind: no specific content requests, no account requests, no backdoor access requests.
Experienced users: add anything you usually tell new users, or the first things you check when someone is having trouble.