Summary

  • ORG-RL110-RIPE and ORG-LR132-RIPE both name RegionInfoCom LLC and publish registration number 1076165010085, while recording different organisation types, maintainers and office suffixes.
  • AS57531 and AS208720 publish reciprocal routing-policy declarations, but registry policy is not a live BGP observation, a topology map, a redundancy test or proof that a customer service uses either system.

One legal number reconciles identity, not operations

ORG-RL110-RIPE names RegionInfoCom LLC, records country RU and registration number 1076165010085, classifies the object as OTHER, and associates it with MNT-REGIONINFOCOM. ORG-LR132-RIPE publishes the same company name and registration number, but classifies the object as an LIR and uses a different maintainer set. The addresses point to the same Rostov-on-Don avenue and building, while their office suffixes differ.

The shared official number is strong administrative evidence that the records refer to one legal registration. It also prevents a common research error: treating two registry handles as two companies merely because their labels and maintenance histories differ. Yet reconciliation must stop where the evidence stops. The records do not say that every customer contract, support team, brand or network component is interchangeable.

Two AS records provide a testable hypothesis

AS57531 uses the name REGIONINFOCOM-AS, refers to ORG-RL110-RIPE and declares import and export policies involving AS31133, AS47626 and AS208720. AS208720 uses ROS-LTD, refers to ORG-LR132-RIPE and declares policies involving AS57531 and the same two external systems. The 185.160.36.0/22 allocation is recorded against ORG-LR132-RIPE with status ALLOCATED PA.

These are precise registry facts. They make several checks possible: observe which origins announce relevant prefixes, compare the observation with the registered policy, identify the customer hand-off, and ask which operating team owns escalation. They do not establish that the declarations are active now, that two apparent paths are physically independent, or that a specific circuit traverses either AS.

Build the service map from the contract outward

A buyer should begin with the contracted legal entity and product, then attach the actual hand-off, address range, observed origin, support queue, restoration owner and remedy. The same registration number can reduce identity ambiguity without reducing operational ambiguity. If failover matters, test it from customer sites and retain timestamped route and reachability evidence. If recovery matters, record who accepts an incident, who can change the network and who owes a credit, termination right or other remedy.

The captured company domains were unavailable during this research. Consequently, no product, tariff, coverage or performance statement from those sites is treated as verified. The registry evidence says nothing about current capacity, latency, availability, congestion or service-level performance.

Sources