fshy

fshy / Debrid

UsenetServer

usenetserver.com · Debrid · 1 record · JSON

UsenetServer Debrid

paidcardcardD

support.usenetserver.com/kb/article/193-i-received-a-423-no- · usenet provider (article spool, NNTP) · debrid/usenetserver · JSON · compare

Free tierNo free tier; a paid usenet account.
unit none; metered on none; No price is quoted because the pricing page was not read.
Pricenone stated
Per-object capNot published; the unit is the article.
Retention'UsenetServer offers one of the highest article retention times available'; no day count on the page read.
EgressUnmetered on an unlimited plan; article availability binds before bytes.
free_allowance: none
Identitycard Paid account with email and card. No identity document described.
Limits
  • retention-clamped articles past retention answer 423 or 430 per article id source
  • request-rate plan connection count is the ceiling; excess connections are refused at connect time source
  • request-rate 50 SSL connections on the 12-month plan, 20 on the 1-month source
  • retention-clamped 6642 days of complete article retention source
The vendor points at indexers as the amplifier: 'Many Indexers maintain references to articles long after they've been removed from Usenet servers', so the NZB can be valid and the articles still gone.
Bindingnone Unlimited bytes; the first failure is a per-article 430/423 whose frequency is set by the indexer's freshness and the spool's retention.
Interfacenntp NNTP reader, TLS; standard article commands.
ToolingSABnzbd, NZBGet, zurg's nzb provider
Composes withThe clearest documented split between the two article codes: 423 means the group is there and the article is not, 430 means the article is unavailable while the group remains readable, which is what a script can branch on.
ReliabilityAn indexer can point at articles the spool no longer holds; each such article is a per-file failure and only PAR2 or a second provider recovers it.
NotesCandidates for the first failure: retention, indexer staleness, or a connection ceiling. The vendor gives a number for none of them; the useful part of this page is the 423/430 split, which lets a client distinguish a missing group from a missing article. A vendor KB article says article access is unrestricted and uncapped that is the only statement about volume on the site.
Evidence rungdocumented The 423/430 distinction and the indexer behaviour are the vendor's own. No removal-by-notice cause is named on this page, which differs from Newshosting's page in the same group.
Checked2026-10-24 (live); stale on 2026-11-23
Evidence (5)
datesourcewhat it proved
2026-10-23support.usenetserver.com/kb/article/193-i-received-a-423-no-'423 No Such Article: The server acknowledges the group exists, but the article requested is not present. 430 No Such Article: The article is not available on the server, even though the newsgroup is accessible.' And 'Many Indexers maintain references to articles long after they've been removed from Usenet servers.'
2026-10-23notes.debridmediamanager.com/providers/usenet/Second server behaviour: a backup account is only asked after every primary has answered no such article; a second server turns a whole-release PAR2 read into one article fetch.
2026-10-23www.usenetserver.com/pricing/$14.95 1 month 20 connections; $8.95 3 months; $7.95 12 months billed $95.40 with 50 connections and US+EU; 6642 days
2026-10-23support.usenetserver.com/kb/article/176-how-much-does-the-seThe same vendor's KB quotes $16.95 1 month, $8.95 exclusive and $7.95 12-month, and 'up to 20 SSL-encrypted connections' - a stale page
2026-10-23support.usenetserver.com/kb/article/183-are-there-any-limits'UsenetServer does not impose restrictions on the number of articles accessed by users.'
More fields (7)
{
 "failure_angle": "missing article",
 "strongest_signal": "430 (article absent) vs 423 (article number absent in a known group)",
 "account_states": "article-level states only on the page read",
 "cache_miss": "not applicable",
 "host_removal": "not applicable",
 "backbone": "Omicron (Highwinds Media), AS33438",
 "conflict": "support KB 176 vs /pricing/ on price and connections"
}