What Is Usenet Completion Rate? How to Test It

Completion rate measures what percentage of articles on a Usenet provider are actually available for download. If a provider claims 99% completion, that means for every 100 article segments in a post, 99 of them are on their servers and downloadable. The missing 1% might have been lost during ingestion, removed by a takedown, or never received from a peer.

Completion rate is one of the most important metrics when evaluating a Usenet provider, but it is also one of the hardest to verify independently. This page explains what affects completion, how to test it, and what the numbers actually mean in practice.

When you download a file from Usenet, your download client needs every segment to reconstruct the original. If segments are missing, the download fails unless there are enough PAR2 repair blocks to fill the gaps.

At 99%+ completion (NewsDemon level), a typical download with standard PAR2 overhead completes without any repair needed. The occasional missing segment gets repaired automatically and you never notice.

At 95% completion, you are losing 5 out of every 100 segments. PAR2 repair kicks in on almost every download. Repairs take time (CPU-intensive), and if the post did not include enough PAR2 data, the download fails entirely.

At 90% or below, large downloads become unreliable. PAR2 repair cannot cover the gaps for many posts, and you end up with incomplete files that cannot be used. This is where people start looking for a second provider to fill in the missing articles.

Backbone quality

A provider on a well-maintained backbone with reliable peering relationships ingests articles more reliably. Missed articles during ingestion are the most common cause of low completion. If a backbone drops articles during peak traffic, every provider on that backbone has the same gap.

Takedowns

DMCA and NTD takedown requests remove specific articles from a provider. Providers on the same backbone share the same takedown processing, so they lose the same articles. Independent providers like NewsDemon process takedowns separately, which means our completion profile is different from the shared network.

Retention depth

Completion tends to decrease for older content. Articles from 10+ years ago have had more time to be affected by hardware failures, storage migrations, and cumulative takedowns. NewsDemon mitigates this with our exclusive tape archive that recovered articles other providers lost during storage transitions.

Storage reliability

Disk failures happen. Providers that run redundant storage architecture (RAID, replication across regions) lose fewer articles to hardware failures. NewsDemon replicates all articles across three server regions.

The only way to truly test completion is to download a selection of NZBs and see what percentage succeeds. Here is a practical approach:

Pick a range of content ages. Try downloading something posted yesterday, something from a month ago, something from a year ago, and something from several years ago. Completion can vary by age.

Check the PAR2 repair stats. After each download, look at your download client logs. SABnzbd and NZBGet both report how many segments were downloaded, how many were missing, and how many were repaired. If you consistently see zero missing segments, completion is very high.

Compare across providers. If you have accounts on two providers, download the same NZB on both and compare the repair stats. This shows you the actual difference in their article inventories.

NewsDemon maintains a 99%+ completion rate across our full retention window. This has been verified by independent review sites including TechRadar and NGR Blog.

Our completion is high because we operate our own backbone with direct peering to other Tier-1 operators, we run redundant storage across three regions, and we recovered exclusive content from tape archives. We do not depend on a shared backbone where someone else controls the ingestion pipeline.