Summary

  • The operator-maintained rdtc.ru page publishes a detailed licence inventory and describes communications services, while RIPE records connect the company name, ORG-RDTC1-RIPE, AS29072 and a sampled route record.
  • Those records are useful identifiers, not proof of current licence status, live routing, service performance or the party responsible for restoring and remedying a particular customer service.

A precise list, with a limited job

Regional Digital Telecommunication Company’s operator-maintained about page says the business was founded in 2000. It lists licence numbers for telematic services, data transmission, communications channels, local telephony and cable broadcasting. The same page says the company serves a range of users from individuals to large companies and banks, and publishes the full Russian legal name and a Novokuznetsk address.

That disclosure has practical value. A procurement team can preserve the licence identifiers, the service class it intends to buy, the legal name shown beside the offer and the date on which the page was observed. It can then seek current confirmation from the relevant authority and attach the applicable terms to the acceptance file.

The page cannot do the authority’s job. In this source set, no regulator response independently confirms whether each listed licence remains current, what conditions apply, or whether a particular product falls within its scope. The claims should therefore remain attributed to the operator site rather than treated as a regulatory verdict.

Registry alignment answers another question

The RIPE NCC member page names Regional Digital Telecommunication Company LLC, gives an address at 45 Kutuzova street in Novokuznetsk and lists the Russian Federation as its service area. The RIPE organisation object names the same company, records country RU and classifies it as an LIR.

The AS29072 aut-num object uses the name RDTC-AS, references ORG-RDTC1-RIPE and has status ASSIGNED. A RIPE Database query for 31.220.160.0 returns an inetnum object for 31.220.160.0 through 31.220.163.255 with netname RDTC-NET, status ASSIGNED PA and maintainer RDTC-MNT. The same query returns a route object for 31.220.160.0/22 with origin AS29072 and the same maintainer.

This is coherent administrative evidence. It gives due diligence a reproducible chain between a company record, an autonomous-system object, an address range and a routing-intent object. It does not show whether the route is visible now, which upstreams carry it, how traffic reaches a customer site, or whether two apparent paths share one physical dependency.

Build the missing recovery map

The acceptance record should join four surfaces without collapsing them. First is the legal and licensing surface: contracting name, current authority evidence and the service class purchased. Second is the resource surface: AS29072, relevant prefixes and the exact network components in scope. Third is operations: the team that monitors the service, receives incidents and coordinates restoration. Fourth is remedy: the entity that owes credits, termination rights or another response when the commitment is missed.

None of the reviewed sources establishes latency, availability, congestion, failover performance or an SLA. None proves that every service on rdtc.ru uses AS29072 or the sampled prefix. A live acceptance test, dated route observations, disclosed upstream and access dependencies, a tested escalation path and contract language are separate evidence.

Sources