What is a Usenet backbone? An explanation of providers and server networks

A Usenet backbone is the underlying server network on which messages and files from newsgroups are received, stored, and made available.

You are downloading a file using SABnzbd, but some articles are missing. Consequently, you purchase a second Usenet account—only to find that this additional news server is also unable to locate those exact same parts. How is that possible?

One possible explanation is that both providers use the same Usenet backbone. In that case, you have two separate accounts, but they are largely backed by the same storage.

Especially when looking for a backup server, it is wise to pay attention to this. Below, we explain what a Usenet backbone is and how to avoid paying twice for essentially the same access.

What is a Usenet backbone?

A Usenet backbone is the underlying server network on which messages and files from newsgroups are received, stored, and made available.

When you open an NZB file in SABnzbd or NZBGet, the actual files are not contained within that NZB file. Instead, the NZB file contains references to the articles that your download program needs to retrieve. This is done via your provider’s news server.

De infrastructuur achter die nieuwsserver bepaalt mede welke artikelen beschikbaar zijn.

You can compare it to two online stores that ship from the same warehouse. Their prices and customer service may differ, but if a product is no longer in that shared warehouse, neither store can supply it.

A provider is not the same as a backbone

Your Usenet provider is the service from which you purchase an account. You receive your login credentials from this provider, and you pay them for a subscription or a data allowance.

Not every provider manages an entirely independent server network. Some providers purchase access from another party and sell it under their own name. Such a provider is called a reseller.

Concept	What does it mean?
Usenet-provider	The provider with whom you open an account
Backbone	Het achterliggende netwerk met servers en opslag
Reseller	A provider that resells access to another network
NZB-indexer	A service that allows you to find NZB files

A reseller is not necessarily a bad choice. The price can be attractive, and the support may work perfectly well. For everyday use, you might not even notice that you are downloading via a reseller.

It becomes especially important when you want to combine multiple accounts.

Why does the backbone make a difference in the case of incomplete downloads?

A file on Usenet is split into many separate articles. Your downloading software retrieves these parts and reassembles them.

If articles are missing, SABnzbd or NZBGet can attempt to repair the damage using PAR2 files. However, this requires a sufficient amount of repair data to be available.

If that doesn’t work, an additional news server might provide a solution—provided, of course, that it contains the missing articles.

Suppose your primary provider can deliver almost the entire download, but a small part is missing. Your backup server has that missing piece, allowing the download to be completed after all.

Do both accounts use the same underlying storage? If so, it is possible that the missing items are absent from both accounts. In that case, switching to a different provider won’t help much.

Do providers on the same backbone always offer the same services?

Not necessarily. Although the storage may overlap, the packages can differ.

Consider factors such as the retention period you get access to, additional servers, or limitations specific to a particular subscription plan. The available speed, number of connections, and customer support may also vary.

Therefore, look beyond just the name of the backbone. Ultimately, you want to know which type of access is included with your package.

If in doubt, ask the provider:

Welke backbone gebruikt dit pakket en krijg ik daarnaast toegang tot andere servernetwerken?

This usually yields a more useful answer than simply asking whether a provider has its own servers.

Using a different backbone as a backup

Do you want to add a second provider to fill in incomplete downloads? In that case, choosing one that relies on a different underlying network is often a logical decision.

You don’t necessarily need to take out a second unlimited subscription for that. A block account might suffice.

With a block account, you purchase a specific amount of data traffic in advance. If you set this account up as a backup, your download software will only use it when the primary server is unable to provide certain items.

An example calculation: a download consists of approximately 20 GB of data to be retrieved. Your primary provider supplies 19.8 GB of this, while the backup server provides the remaining 0.2 GB. In this case, only the traffic routed through the backup server is deducted from your block account, in accordance with the provider’s measurement method.

In this way, a data allowance can last a long time. Naturally, this depends on how much you download and how often your main server is missing components.

Also read our article about Usenet block accounts if you would like to know more about this combination.

How do you check which backbone your provider uses?

Start with the information provided by the service provider itself. Check the product page, the frequently asked questions (FAQs), or the technical documentation.

Can’t find it? Ask customer service about the infrastructure of the specific package you are using.

Online backbone overviews can be helpful, but pay attention to the date. Providers may switch to a different network. Furthermore, packages can change or gain access to additional servers.

An overview that was accurate a few years ago may no longer be suitable to base your purchase on.

When does an additional backbone fail to help?

Not every failed download is caused by missing items.

For example, a second provider won’t help if your hard drive is full, your download program lacks write permissions, or an archive requires a password.

Even if articles are missing, switching to a different backbone offers no guarantees. The upload may have been removed from both networks, or it may fall outside the available retention period.

Therefore, first check the error message. If it concerns missing items, trying a different server might be useful. If it relates to unpacking, storage space, or permissions, you will need to look for the problem elsewhere.

You can find further explanation in our guide: Usenet download incomplete – what to do?

Not every failed download is caused by missing items.

For example, a second provider won’t help if your hard drive is full, your download program lacks write permissions, or an archive requires a password.

Even if articles are missing, switching to a different backbone offers no guarantees. The upload may have been removed from both networks, or it may fall outside the available retention period.

Therefore, first check the error message. If it concerns missing items, trying a different server might be useful. If it relates to unpacking, storage space, or permissions, you will need to look for the problem elsewhere.

Do you need multiple Usenet backbones?

If your downloads almost always arrive complete, there is little reason to purchase additional accounts.

An additional backbone only becomes worthwhile if you frequently encounter missing articles. In that case, you might want to start with a small block account and see if it improves your results.

Pay particular attention to the downloads that succeed thanks to the backup. A server doesn’t need to provide much data to be useful; however, if it consistently lacks the same items as your primary provider, the account likely adds little value.

So, check what you already have before choosing a second provider. Two different names on your bill do not necessarily mean two different sources for your downloads.