A Usenet backbone is the core server infrastructure operated by Tier-1 providers that stores, exchanges, and propagates every article posted to Usenet newsgroups. These backbone networks peer with each other to synchronize content across the entire decentralized system.
If you have ever tried to download an archived file from Usenet only to find articles missing, the answer almost always traces back to which backbone your provider sits on. Understanding the backbone structure is one of the most practical things a data hoarder can learn.
The Usenet backbone map is a visual diagram showing how Usenet servers, providers, and resellers connect to each other. It makes an otherwise invisible infrastructure easy to reason about, even for beginners.
In this guide, we walk through what the backbone actually is, how to read the map, which major backbone families exist today, and how to build a smart multi-provider setup for better archive recovery.
Table of Contents
What a Usenet Backbone Actually Is
The backbone is not one server or one company. It is a collection of large, interconnected server farms operated by Tier-1 Usenet providers that peer with each other and exchange data feeds continuously. Every article posted anywhere on Usenet eventually propagates to every peering backbone.
How Backbone Servers Power Netnews
Backbone servers are the heavy infrastructure of netnews. They store massive volumes of binary and text content and replicate it to every peer they connect with. When a user posts an article, it does not stay local; the originating server pushes it outward across every peered backbone.
This replication is what gives Usenet its resilience. No single server holds everything, and no single failure wipes out the archive. Each backbone maintains its own copy of the propagated content independently.
Retention, the length of time a backbone keeps articles available, varies between operators. That difference matters enormously for archival data organizers chasing older content.
Why Tier-1 Access Is Different From Reselling
Tier-1 Usenet providers own and operate their own server hardware. They control their own network, set their own retention policies, and sell access directly to consumers or wholesale to resellers.
A reseller buys gigabytes or connection slots from a backbone and packages them under its own brand. The reseller does not own the servers. This means a reseller’s content availability, retention ceiling, and takedown behavior are all determined by whatever backbone sits upstream.
Knowing whether your provider is a direct Tier-1 operator or a reseller tells you exactly whose infrastructure you are actually paying for.
How Articles Propagate Across Multiple Servers
When an article is posted, the originating server sends it to every server it peers with. Each of those servers then forwards the article to their own peers, minus servers that already have it. This flood-fill propagation continues until every backbone in the network holds a copy.
The process is fast, usually completing within minutes for popular newsgroups. The practical consequence is that the same binary archive exists on every peering backbone simultaneously, though takedowns and retention limits can create divergence over time.
How To Read a Usenet Backbone Map
A Usenet backbone map uses color-coded nodes and connecting lines to represent backbone operators, Tier-1 providers, resellers, and the peering relationships between them. Server locations, ASN identifiers, and connection paths all add layers of context that make the diagram genuinely useful rather than decorative.
What the Usenet Map and Provider Map Show
The provider map at NGProvider uses distinct colors to separate three categories. Red nodes represent backbones, the top-level operators. Blue nodes represent Tier-1 providers that have their own servers but may also resell. Grey nodes are resellers with no dedicated infrastructure of their own.
Lines between nodes show peering or reseller relationships. A line from a grey reseller node up to a red backbone node means that reseller buys its feed from that backbone. A line between two red backbone nodes means those operators peer and exchange data directly.
The Usenet Tree at Usenet Deals renders a similar hierarchy as a navigable tree diagram, which some readers find easier to follow than a node graph.
How To Spot Parent Networks and Reseller Relationships
Every grey reseller node connects upward to at least one backbone. That upstream connection is the reseller map telling you exactly where the content actually comes from. If two services you are comparing both connect to the same red backbone node, they are serving the same data, subject to the same retention and the same takedowns.
The Wikimedia Commons backbone diagram maintained by the community provides a clean snapshot of the current landscape and is updated periodically as provider relationships change.
How Server Locations, ASN, and Connections Add Context
Server location labels on the map show where physical infrastructure sits, commonly the United States, Netherlands, Germany, and France. An ASN, or Autonomous System Number, is a unique identifier assigned to each independently operated network on the internet. Two providers sharing an ASN are almost certainly on the same backbone, regardless of different brand names.
Connection count matters too. A backbone peering with many other backbones has better propagation coverage than an isolated one. More connections generally mean faster article spread and fewer propagation gaps.
Major Backbone Families and Common Provider Relationships
Several distinct backbone families dominate the current Usenet landscape, each with its own cluster of resellers and subsidiary providers. Knowing which family each provider belongs to is the fastest way to avoid paying twice for identical content.
Omicron, Eweka, and Base IP
Omicron Media operates one of the backbone families frequently referenced in community-maintained maps. Several consumer-facing providers trace their feed back to the Omicron backbone, making it a significant but sometimes overlooked infrastructure player.
Eweka Internet Services is a well-regarded Dutch backbone with a strong reputation for long retention and stable completion rates. Eweka operates directly and also feeds a number of resellers, primarily serving European markets, though its articles propagate globally through peering.
Base IP appears in the backbone map as a separate red-node operator, meaning it runs its own infrastructure and peers independently. Some providers that appear distinct at the consumer level are actually drawing from Base IP upstream.
UsenetExpress, Vipernews, and Uzo Reto
UsenetExpress is a backbone operator that feeds a notable cluster of consumer-facing resellers. According to community discussion on Reddit’s r/usenet, NewsDemon is one example of a provider that sources from the UsenetExpress backbone.
Vipernews is listed as a backbone entity on the NGProvider map, operating its own server infrastructure independently of the other major families. Uzo Reto appears in community-maintained maps as a connected operator within this cluster.
Abavia, usenet.farm, Giganews, Netnews, and Its Hosted
Abavia and HW Media appear in community maps as interconnected backbone entities, sometimes sharing infrastructure or peering relationships. The Reddit backbone map thread notes Abavia’s relationship with HW Media as a dual-backbone arrangement.
Usenet.farm operates as its own backbone with a reputation for high retention figures. Giganews, one of the oldest names in Usenet, operates under the UNS Holdings umbrella. The NGProvider backbone overview identifies UNS Holdings as running infrastructure in the United States, Netherlands, and Germany. Netnews and Its Hosted connect into this family as related entities under the same parent structure. United Newsserver and Supernews are additional providers that connect through this cluster.
Retention, Takedowns, and Why Availability Differs
Retention and takedown policy are the two main reasons the same archived file can be perfectly complete on one backbone and severely damaged on another. Both factors are worth understanding before choosing a provider.
What Retention Really Tells You
Retention is measured in days and refers to how long a backbone keeps articles stored on its servers. A provider advertising 5,000 days of retention means articles posted up to roughly 13 years ago are theoretically still accessible.
High retention numbers matter most to archival data organizers hunting older public domain assets or rare releases. As noted in community discussions about binary retention, providers like Eweka and Easynews are specifically valued for long-term article availability.
Retention figures reflect a ceiling, not a guarantee. Takedowns can remove individual articles well before the retention window expires.
DMCA vs NTD in Practical Terms
DMCA takedowns apply under United States law. When a rights holder sends a valid DMCA notice, US-based backbones are legally required to remove the specified articles. Backbones operating exclusively under Dutch or German jurisdiction respond instead to NTD, or Notice and Takedown, procedures, which follow different legal frameworks.
As explained in NewsDemon’s breakdown of Usenet takedowns, jurisdiction matters because US-based and EU-based backbones may respond differently to the same complaint. An article removed from a US backbone under DMCA may still be intact on a Dutch backbone under NTD rules, or vice versa.
Why the Same Archive Can Be Complete on One Network but Not Another
Each backbone handles its own takedown queue independently. When a takedown removes articles from one backbone, peered backbones do not automatically remove the same articles. The result is that completion varies across the network.
According to SABnzbd forum guidance on missing articles, combining access to multiple providers on different backbones is the most reliable way to fill gaps. A file that is incomplete on your primary backbone may be fully intact on a secondary one.
Backbone Diversity for Better Archive Recovery
Backbone diversity is the practice of maintaining accounts on servers from at least two distinct, non-overlapping backbone families. It is the single most effective strategy for completing damaged or partially missing archives.
Why One Primary Usenet Account Is Often Not Enough
A single Usenet account gives access to exactly one backbone’s copy of the article database, subject to that backbone’s retention limits and takedown history. For casual text browsing, that is usually fine.
For archival data organizers storing high-resolution media, public domain datasets, or rare publications, a single account creates a single point of failure. Anything removed or expired on that backbone is simply gone from your perspective.
How a Block Account Complements Unlimited Access
A block account is a prepaid data allocation, often sold in sizes like 50 GB or 500 GB, purchased from a provider on a different backbone than your primary subscription. You use the block account only when your main provider reports missing articles.
Newshosting’s explanation of backbone diversity describes this exact approach: a primary unlimited account for day-to-day use, with a cheaper block account on a separate backbone as a fallback for filling gaps. Most good newsreaders, such as SABnzbd, support automatic fallback to a secondary server when articles are missing on the primary.
The block account rarely empties quickly because it only activates for missing content, making it a cost-effective complement.
How To Avoid Paying Twice for the Same Backbone
The only way backbone diversity works is if the two accounts genuinely draw from different upstream networks. Consulting the backbone map at NGProvider or the Usenet Tree before purchasing a secondary account reveals whether two candidate providers share a parent backbone.
If both providers connect to the same red backbone node on the map, buying both accomplishes nothing for recovery purposes. The article gaps on one will be identical gaps on the other.
Choosing a Sensible Provider Mix
Choosing providers with backbone diversity in mind means looking past brand names and pricing to the underlying infrastructure. The community-maintained maps and comparison tools make this easier than it used to be.
Examples of Direct Providers and Resellers Readers Will Encounter
The Usenet market contains a mix of direct Tier-1 operators and resellers. Newshosting, UsenetServer, and Easynews are frequently cited as providers with their own substantial infrastructure. Newsgroup Ninja, AstraWeb, NewsgroupDirect, NewsDemon, and TheCubenet appear in community maps as providers that may draw from established backbones including UsenetExpress and others.
Providers like Thundernews, UsenetPrime, MaximumUsenet, NovaUsenet, UsenetNow, BlockNews, Frugal Usenet, XS News, BulkNews, CheapNews, XS Usenet, StingyUsenet, XLned, UsenetBucket, Usenet.org, Usenet.nl, UseNeXT, EasyUsenet, and NewzLeecher occupy various positions on the map, some as direct operators and some as resellers. The comprehensive provider list at Usenet.org tracks backbone affiliation, server location, retention, and privacy policy across more than 60 providers in one place.
How To Compare Price, Privacy, and Server Region
Price per gigabyte or monthly subscription is the obvious starting point. After that, look at the provider’s logging policy and jurisdiction. A provider based in the Netherlands operating under Dutch law has different obligations than a US-based operator responding to DMCA requests.
Server region affects latency and sometimes download speed. European archival data organizers benefit from providers with Netherlands or Germany infrastructure. North American users typically see better speeds from providers with US-based server nodes.
UsenetCompass is a community tool that maps backbone affiliation and lets readers filter providers by backbone, which simplifies the comparison process significantly.
When To Add a Secondary Account for Coverage
The case for a secondary account is strongest when you are working with older archived content or content from newsgroups with high takedown activity. If your primary provider regularly reports article not found errors during downloads, that is the clearest sign that backbone diversity would help.
Get Newshosting for a reliable Tier-1 primary account, then pair it with a block account from a provider on a confirmed different backbone. That combination covers the vast majority of recovery scenarios without significant ongoing cost.
Frequently Asked Questions
How can I tell which backbone a specific Usenet provider uses?
The fastest method is to check the NGProvider backbone map or the Usenet.org provider list, both of which list backbone affiliation by provider name. The UsenetCompass tool also allows filtering by backbone. If a provider is not listed, searching the provider name on the r/usenet subreddit usually surfaces a community-sourced answer.
What are the main Usenet backbones and which providers resell each one?
The major backbone families currently active include UNS Holdings (which covers Giganews), Eweka, Base IP, UsenetExpress, Vipernews, Omicron Media, Abavia, and Usenet.farm. Each of these operates its own server infrastructure and feeds a varying number of reseller brands. The exact reseller map shifts over time as commercial relationships change.
Are there any tools or methods to verify a provider’s backbone and retention claims?
Community-maintained resources like the Usenet backbone map on Wikimedia Commons, the NGProvider maps, and UsenetCompass all aggregate backbone affiliation data. Retention claims are harder to independently verify, but the Big-8 Management Board’s paid provider list includes geographic and structural information that helps cross-reference what providers advertise.
How often do provider-to-backbone relationships change, and where can I find up-to-date info for 2025-2026?
Provider relationships change when companies are acquired, when wholesale agreements shift, or when a reseller moves to a different upstream. These changes happen a few times per year across the industry. The most current information is typically found in the r/usenet subreddit, the NGProvider map, and the Wikimedia Commons backbone diagram, which carries version dates indicating when it was last updated.
Which backbones offer the best completion rates and retention for popular newsgroups?
Eweka is frequently cited in the community for high retention and strong completion on binary newsgroups. UNS Holdings infrastructure, including Giganews, is also considered among the more complete and long-running options. Usenet.farm has a reputation for high retention figures. The honest answer is that completion varies by newsgroup, content type, and recent takedown activity rather than by backbone alone.
How do I choose between two providers if they appear to use the same upstream network?
If two providers share the same backbone, the differentiating factors become price, privacy policy, server region, customer support, and the number of simultaneous connections offered. From a content availability perspective, the two accounts are functionally equivalent. In that case, it makes more sense to pick the cheaper or better-supported option and put the savings toward a block account on a genuinely different backbone for recovery purposes.