Usenet network

Usenet is not one central database. It is a loose federation of servers that share articles through peering. A post on one well-connected server eventually propagates to others—though speed and completeness depend on the path it takes.

Peering and propagation

News servers exchange articles with trusted peers. When someone uploads to a group, those articles fan out across the network. Propagation is usually minutes to hours, not instantaneous. Missing parts on one backbone may exist on another, which is why multi-network providers matter.

Backbones and upstream networks

Large commercial backbones carry huge volumes of groups and retention. Retail providers like Hydra connect to one or more upstream networks and route fetches intelligently so you get better completion without managing peering yourself.

View live upstream status on our peering page.

Why one server hostname is enough

You connect to Hydra’s regional endpoint; behind that, the exchange selects routes across connected networks. You do not need separate accounts for each backbone—your client only sees the Hydra hostname and credentials.

Retention across the network

Retention is per-server. An article deleted on one peer may still exist elsewhere until its retention expires. Hydra advertises deep retention on its tiers; actual availability still depends on whether all parts propagated and remain on reachable backbones.