Summary

  • RIPE organisation object ORG-RA21-RIPE, whose org-name is JSC "ER-Telecom Holding" (country RU, reg-nr 1065902028620, org-type LIR), is recorded as the holder of autonomous systems that still carry legacy regional as-names: RAID-R-AS, NEWTELESYSTEMS, AS-SIBTELECOM, ASN-KRAFTSVIAZ, URAL and the transit AS ERTH-TRANSIT-AS.
  • Two of those holder attributions rest on RIPEstat, the RIPE NCC's own resource service; four rest on third-party mirrors of RIPE data and have not been confirmed against the registry's own service in this review.
  • No last-modified timestamp for any of the objects, and no corporate filing, annual report or transaction document from the group, was obtained. The record therefore supports a holder-of-record statement and nothing about ownership, revenue or market share.

What the record layer shows

A single RIPE organisation object sits under these networks. ORG-RA21-RIPE carries the org-name JSC "ER-Telecom Holding", country RU, registration number 1065902028620 and org-type LIR (AS47398 object). The same organisation is recorded as the holder of several autonomous systems, each of which continues to advertise a name from an earlier corporate life.

AS31692 carries the as-name RAID-R-AS, with the allocation listed as 2004-07-14, country RU, status ALLOCATED (RIPEstat, AS31692). AS31036 carries the as-name NEWTELESYSTEMS, allocation listed 2004-02-12, the same holder (RIPEstat, AS31036). AS47398 carries the as-name AS-SIBTELECOM and its contact records still reference Sibtelecom Ltd. in Irkutsk (AS47398 object). AS21311 retains the legacy as-name ASN-KRAFTSVIAZ, with remarks referencing the ERTH network (AS21311 object). AS5563 carries the as-name URAL, described as Ural Regional Net, Ekaterinburg (AS5563 object). The AS9049 object header gives as-name ERTH-TRANSIT-AS, with remarks identifying it as the ER-Telecom transit AS, under the same organisation handle (AS9049 object).

The pattern is legible: the holder field has converged on one legal entity while the as-name field still names the regional businesses that were built, or bought, separately.

Where the evidence is strong, and where it is not

RIPEstat is operated by the RIPE NCC, so the AS31692 and AS31036 attributions come from the registry's own resource service. The other four do not. AS9049 is drawn from Hurricane Electric's BGP Toolkit, and AS47398, AS21311 and AS5563 from IPIP.NET and IPInsight.io — mirrors of RIPE data rather than the registry itself.

That distinction is not pedantry. A mirror reproduces an object as of the last time it synchronised, and none of the pages captured here exposes a current last-modified timestamp. Before the four mirror-based attributions carry the same weight as the two RIPEstat ones, they should be checked against the registry's own service. Until then, the honest formulation is that one organisation handle is recorded as holder across the set, with the strength of that statement varying by object.

A holder field is not a control finding

It is worth being precise about what a registry holder field is. It is the registry's own record of who holds a number resource. It is an administrative attribution maintained by a registry; it is not a court finding, a shareholding register entry, a valuation or a market-share measurement. Reading it as proof of corporate control, group revenue or pricing power would import claims that no source in this review supports.

The gap is easy to state. No annual report, securities filing, transaction document or press release from JSC "ER-Telecom Holding" was obtained. No acquisition date, consideration, ownership percentage or subscriber figure was obtained. The record layer can therefore say who the registry records as holder; it cannot say how large the group is, who ultimately owns it, or what share of any national market it serves. Those are documentary questions, and they are answered by filings, not by reading the registry more closely.

The naming layer still describes a federation

An as-name is a descriptive label carried inside the registry object. It is not the holder-of-record field. That is why the two layers can move at different speeds: a holder field can be updated in a registry operation while the as-name, the route objects that reference it, the IRR entries and the abuse-contact records continue to point at an older identity.

The practical consequence is coordination, not ownership. When legal identity has consolidated but network identity has not, an engineer reading a route object, a compliance analyst checking an abuse contact, a peering coordinator resolving an as-name and a customer recognising a brand may each arrive at a different operator name for the same traffic. For the group, that is a transition cost. For a counterparty, it is a documentation surface that a holder-field change does not close.

What the Dom.ru question does and does not show

The consumer-facing name Dom.ru appears as no registry object in the material reviewed here. That is a null capture, not a finding of absence. A consumer brand sits outside the RIR object model by construction, so a registry search is not the instrument that would establish anything about it. A brand-layer claim would need trademark, domain or corporate filing evidence, none of which was obtained.

What would change the assessment

Three retrievals would materially move this picture. First, the full RPSL objects for ORG-RA21-RIPE and each autonomous system, read directly from the registry, together with their last-modified timestamps — which would date the holder-field consolidation and allow it to be ordered against the naming residue. Second, a corporate filing or transaction document for each named regional operator, which would close the gap between record-layer consolidation and corporate consolidation. Third, any registry object or trademark record carrying the Dom.ru name, which would move the brand question from uncaptured to evidenced.

Until then, the defensible statement is narrow and still useful: the registry records one legal entity as holder of a set of networks whose names belong to an earlier era, and the naming layer has not caught up.