Summary

  • NPO Unimach is a real Russian legal company and RIPE NCC member, but the public evidence does not establish it as a retail or wholesale Internet provider. Its registered principal activity is property leasing and administration, while the current Unimach machinery site identifies a different legal company, NPK Morsvyazavtomatika, as the manufacturer and user of the brand.
  • The network footprint is substantive but compact. RIPE data observed AS207853 announcing one IPv4 /24 and two IPv6 prefixes on 10 July 2026, with full visibility among the reporting IPv4 and IPv6 collectors. That proves active routing control, not a subscriber base or telecom revenue.
  • RIPE observed three upstream-side neighbours: NPK Morsvyazavtomatika's AS207822, Petersburg Internet Network's AS44050 and ER-Telecom's AS9049. Multiple visible neighbours reduce dependence on one routing relationship, but public data cannot show whether the circuits use separate ducts, buildings, power, routers or operating teams.
  • The commercial website and mail for unimach.ru resolved through AS207822 rather than NPO Unimach's AS207853 when checked. The two networks also register reciprocal backup policies. This looks more like affiliated operational resilience than independence from the wider industrial group.
  • Registry-derived accounts report 2024 revenue of RUB581.945 million, cost of sales of RUB552.507 million, gross profit of RUB29.439 million and net profit of RUB19.393 million. The resulting gross margin of about 5.1% and net margin of about 3.3% leave little room for network spending that does not prevent measurable loss.
  • A one-percentage-point cost against revenue would equal about RUB5.82 million, roughly 30% of reported net profit. NPO Unimach therefore needs outage-loss, service-level and replacement-capital evidence, not a count of addresses, to prove that network ownership creates value.
  • The conclusion is negative but conditional: AS207853 is credible insurance for a digitally dependent industrial site, yet there is no public proof that customers pay for it, that the paths are physically independent, or that its return exceeds a managed dual-carrier alternative. Until those facts are disclosed, the network should be valued as a cost-control and continuity asset, not a growth business.

Independence is an insurance policy before it is a product

The incentive to own an autonomous system is strongest when losing a connection costs more than buying a second one. A manufacturer can lose access to order files, remote support, supplier portals, payment services, software updates and communications. A property owner can lose building controls, tenant services and administrative access. An industrial group can lose coordination across engineering, sales and after-sales teams. None of those losses requires the company to sell Internet access. They require only that digital interruption is expensive.

Provider-assigned addressing is convenient until the provider changes. The customer receives a circuit, a block of addresses and a default route, while the carrier handles global reachability. That arrangement is usually cheaper to operate because it avoids direct registry administration and reduces the need for internal routing expertise. Its weakness is bargaining power. Changing carrier can require renumbering externally reachable services, revising firewall rules, coordinating remote users and accepting a migration window in which the old provider remains operationally important.

An autonomous system and portable or provider-aggregatable resources can alter that negotiation. The company can announce its own prefixes through more than one upstream, preserve addressing through a carrier change and choose routing policies instead of accepting one provider's defaults. The option has value even when it is rarely exercised. A credible ability to leave a supplier can improve contract terms, while a second active route can carry traffic when the first fails.

The option is not free. Someone must buy or lease routers capable of carrying the required routes, maintain configurations, monitor reachability, secure administrative access, renew support, keep spare optics and power equipment, investigate abuse reports and coordinate with carriers. Someone must understand why a route was withdrawn at 03:00. A second circuit also becomes false comfort when it enters through the same duct, terminates on the same device or depends on the same electricity supply.

That makes the correct economic question narrower than whether NPO Unimach "has a network." It plainly does. The question is whether the reduction in expected outage loss, switching cost and supplier power exceeds the annual cost of maintaining that control. If no external customer buys connectivity, every ruble of return must appear elsewhere: fewer interrupted orders, less idle machinery, faster recovery, protected rental income, lower migration cost or stronger negotiating leverage.

This distinction matters because Internet number resources are visually impressive. A large IPv6 allocation can contain an astronomical number of addresses. Those addresses do not produce revenue. They are an addressing architecture. An autonomous system can be globally visible without carrying much traffic. Three upstream relationships can exist without three physically independent routes. Strategy begins when resource control changes loss probability or commercial terms; before that, it is an engineering capability looking for a financial justification.

The legal company, the machinery brand and the network are not the same boundary

NPO Unimach's public identity has three overlapping layers. They should not be collapsed.

First, the legal company is specific. A registry-derived company profile identifies NPO Unimach LLC by registration number 1117847480057 and tax number 7811505767. It was registered on 8 November 2011 at Kibalchicha Street 26E in St Petersburg. The profile lists Andrian Pravdin as chief executive and 60% owner, with Andrey Smirnov owning 40%. Its principal registered activity is leasing and administration of owned or rented real estate, accompanied by manufacturing and engineering activities.

Second, the Unimach commercial identity is broader and has changed in its legal presentation. A 2019 equipment catalogue described NPO Unimach as the machine-tool operation within a larger industrial grouping and presented laser-cutting systems, in-house manufacturing and industrial customers. The current company page, by contrast, says NPK Morsvyazavtomatika develops and manufactures the equipment and uses the Unimach trademark. The current home page says that company has supplied more than 1,700 machines since 2007. Those claims describe the present brand operator; they cannot automatically be booked as NPO Unimach's sales, installed base or service obligations.

Third, the network resource holder is again specific. The RIPE NCC member entry names "NPO Unimach" LLC, gives the same Kibalchicha Street 26E address and lists Russia as the area serviced. RIPE's organisation record connects that holder to Russian registration number 1117847480057. This is strong identity evidence. It tells us which legal company holds the membership and resources. It does not tell us which group companies use each address, which company pays each circuit invoice or how network costs are allocated.

The shared address is economically important. A 2025 report by Delovoy Peterburg said NPO Unimach and NPK Morsvyazavtomatika had the same 60/40 ownership split and reported that a 1,500-square-metre non-residential building had been built for NPO Unimach in 2021. This supports the possibility that NPO Unimach acts partly as an asset or property vehicle inside an industrial perimeter. It does not establish the terms under which any affiliated operation uses the property or network.

The accounts reinforce the need for boundary discipline. A company can own a building, earn rent, commission research, hold Internet resources and support related operating businesses without being the entity shown on a product website. NPO Unimach did commission technical work in its own name: a 2024 appellate decision records a dispute over a 2021 research and development contract for a laboratory hydrocarbon-conversion prototype. That is evidence of an active commercial and technical role. It is not evidence of Internet access sales.

The narrow conclusion is more useful than a broad label. NPO Unimach controls an active autonomous system and number resources. It is publicly associated with an industrial site and a machinery history. The current brand operator is another legal company at the same address, and the public record does not disclose an intercompany network agreement. Any analysis of revenue or customers must therefore stay at the NPO Unimach legal-company boundary unless a source explicitly says otherwise.

What the evidence does not permit

It does not permit treating the RIPE phrase "areas serviced: RU" as a claim that NPO Unimach sells broadband across Russia. RIPE member pages use service-area terminology for registry members, including enterprises that operate networks for their own purposes. It does not permit counting every Unimach machine as a network customer. A machine buyer may use software, remote service or online support, but there is no public offer showing that NPO Unimach sells those buyers connectivity through AS207853.

It also does not permit assuming that common owners eliminate commercial friction. Related companies can charge rent, connectivity, software, labour or support to one another. They can allocate profitable activities and capital costs differently. The same owners may prefer group resilience even when one legal company bears more cost than benefit. Without contracts or segment reporting, group logic and company-level value are not interchangeable.

This is the first test NPO Unimach must pass. If the network protects several operations at Kibalchicha Street, the company needs a cost-sharing method tied to capacity, criticality or avoided loss. If it absorbs the cost while another company receives most of the benefit, AS207853 can be rational for the owners and a poor return for NPO Unimach itself.

The routing record proves a small active network

The public technical evidence is unusually clear. RIPE assigned AS207853 on 15 November 2019. The autonomous-system record names NPO-UNIMACH-AS, ties it to the NPO Unimach organisation record and remained assigned after an update in May 2026. RIPE's routing-status data says the network was first observed in global routing on 3 December 2019 and remained visible on 10 July 2026.

As of the research date, RIPEstat's announced-prefix view showed three prefixes originated by AS207853:

  • 91.210.152.0/24, containing 256 IPv4 addresses;
  • 2001:678:b9c::/48, an IPv6 provider-independent assignment; and
  • 2a07:b1c0::/29, an IPv6 allocation made after NPO Unimach became an LIR.

The routing-status view reported that every one of the 327 reporting IPv4 collectors and every one of the 321 IPv6 collectors could see the relevant announcements. It counted one IPv4 prefix, two IPv6 prefixes and three observed neighbours. That is meaningful operating evidence. The routes were not dormant database entries or low-visibility experiments at the time of observation.

The chronology also makes sense. The provider-independent IPv6 /48 and autonomous system were assigned in November 2019. RIPE created the LIR organisation record in June 2020, then allocated the IPv4 /24 and IPv6 /29. A company that wanted only a single carrier connection would not need this structure. The sequence suggests a deliberate move from independent IPv6 presence toward broader direct resource control.

Yet scale must be read correctly. The /24 is the smallest conventional IPv4 block that is normally accepted across the global routing table without being filtered as too specific. It is useful for a modest enterprise estate, externally reachable services, network devices and customer or tenant segments. It is not evidence of thousands of subscribers. The two /25 assignments inside the block are both named for NPO Unimach in the RIPE database; no public sub-assignment identifies an external customer.

The IPv6 numbers are even easier to misuse. A /29 contains 524,288 separate /48-sized networks. That does not mean NPO Unimach has 524,288 sites or any comparable commercial scale. IPv6 allocation policy deliberately provides room for structured addressing and long-term growth. The economic evidence is adoption: active use, configured services, traffic, customers, operational savings and avoided complexity. The public record shows the /29 announcement but not utilisation inside it.

An AS-set record adds one revealing detail. AS-SET-UNIMACH contains AS207853 and AS207822. The second network belongs to NPK Morsvyazavtomatika. This allows upstreams using registry policy to accept announcements for both networks under the set. It is evidence of coordinated routing policy, not proof that either company owns the other's assets.

The network is therefore neither imaginary nor large in the sense relevant to a commercial carrier. It is a compact dual-stack enterprise presence with enough structure to support multihoming and group-level continuity. That is an appropriate scale for insurance. It is weak evidence for a connectivity growth thesis.

Three observed neighbours are useful, but they are not three independent networks

On 10 July, RIPEstat observed three upstream-side neighbours for AS207853: AS207822, AS44050 and AS9049. Public records identify them as NPK Morsvyazavtomatika, Petersburg Internet Network and ER-Telecom respectively.

The diversity is real at the routing-contract level. NPK Morsvyazavtomatika is an affiliated industrial operator with its own LIR and autonomous system. Petersburg Internet Network's PeeringDB entry describes AS44050 as a St Petersburg access and network provider. ER-Telecom's entry describes AS9049 as a much larger network service provider with a broad geographic and interconnection footprint. NPO Unimach is not reliant on a single observed external carrier.

The registered policy has been broader than the observed state. AS207853's RIPE record names AS44050, AS8492, AS25408 and AS9049 as upstreams, with AS207822 under a backup heading. AS8492 is OBIT; AS25408 is another Russian network. The July observation did not show AS8492 or AS25408 as current neighbours. Registered policy can remain after a circuit is inactive, be prepared before service begins, or represent a path that collectors do not see. Observed routing is stronger evidence of the current public path set, while the registered record shows supplier optionality or history.

The relationship with AS207822 deserves more weight than a normal carrier link. Its RIPE record registers a reciprocal backup policy: NPK Morsvyazavtomatika accepts a route from AS207853, while NPO Unimach accepts a route from AS207822. RIPEstat saw AS207853 on the downstream side of AS207822 and saw AS207822 on the upstream side of AS207853. In practical terms, the affiliated network was one route from NPO Unimach toward the wider Internet on the observation date.

Public DNS offered a second clue. The unimach.ru website address resolved to 94.142.128.41, which RIPEstat associated with AS207822 rather than AS207853. The mail exchanger was mx.unicont.com, also resolving inside AS207822's 94.142.128.0/24. Meanwhile, reverse DNS for 91.210.152.1 inside NPO Unimach's own /24 named bgp.unimach.ru. The public-facing brand services sit on the affiliated network; the NPO block exposes at least a routing-related name.

This arrangement can be economically sensible. Hosting web and mail on an affiliated network means those services need not disappear merely because AS207853 is withdrawn. NPO Unimach can use AS207822 as a backup route while maintaining external carrier options. Two resource holders can support one industrial site and preserve separate administrative control.

It also limits the independence claim. If both networks share the same address, owners, server room, electricity supply, staff, firewall cluster or entrance duct, one local failure can remove both. If AS207822 provides DNS, mail, hosting and a backup path, a configuration error or security incident there can affect several services at once. BGP diversity protects against some carrier and route failures. It does not automatically protect against site, power, human or equipment failures.

The missing evidence is physical. NPO Unimach does not publish carrier handoff locations, route maps, duct entrances, power sources, router pairs, service-level commitments or failover tests. It should not publish sensitive diagrams, but it can disclose the economic outputs: the number of physically diverse carrier entrances, successful failover tests, annual minutes of correlated outage and mean restoration time. Without those results, three observed neighbours are a promising architecture rather than proven redundancy.

The business model is probably internal resilience, not paid transit

There are three possible ways AS207853 could earn a return.

The first is direct sale. NPO Unimach could charge outside customers for Internet access, managed networks, hosting, addresses or related services. Public evidence for that model is weak. The company's principal registered activity is property, the current Unimach site sells industrial machinery under another legal entity, and PeeringDB's API returned no network entry for AS207853. RIPEstat observed no downstream-side autonomous system neighbours. None of those facts proves that no customer exists: small customers normally do not have autonomous systems, and PeeringDB participation is voluntary. Together, however, they provide no support for a material carrier business.

The second is intercompany service. NPO Unimach may provide connectivity, addressing, hosting or continuity to businesses at the same industrial site and recover cost through rent or service charges. The common address, shared owners, AS-set and reciprocal routing policy make this plausible. No public agreement shows the price, users, capacity or margin. If charges merely move money among commonly owned companies, revenue can rise without group value creation. The relevant gain is still avoided external cost or avoided disruption.

The third is self-provisioned continuity. The network can protect NPO Unimach's own property, research, administrative and industrial functions. This is the most defensible public interpretation. It does not need a telecom product page. It needs critical applications, more than one route and a financial case for keeping them available.

That case should be built as expected loss. Suppose an outage has a 10% annual probability and would cost RUB20 million through idle work, missed delivery, recovery and penalties. Avoiding half of that expected loss is worth RUB1 million a year. If network independence costs less than RUB1 million more than a managed alternative, it creates value. If the likely outage costs RUB2 million, the same architecture is excessive. The figures here are illustrative, not estimates of NPO Unimach's operation; the public record does not provide the inputs.

The exercise forces strategy into resource allocation. Reliability is not valuable because engineers prefer it. It is valuable because an identified cash flow, asset or obligation would otherwise be exposed. NPO Unimach should know which applications are protected, their tolerated interruption, the revenue or cost at risk and which failure modes the second route actually removes.

The direct-sale model would require different evidence: customer count, monthly recurring connectivity revenue, contracted capacity, churn, support staffing, gross contribution and bad-debt rates. None is disclosed. Treating AS207853 as an ISP because it has an ASN would reverse the burden of proof. The network should be valued as internal infrastructure until commercial accounts show otherwise.

Revenue grew, but the margin leaves little room for unmeasured resilience

The legal company's reported accounts provide the hardest financial constraint. The RBC Companies profile reports 2024 revenue of RUB581.945 million, compared with RUB516.282 million in 2023. That is an increase of RUB65.663 million, or about 12.7%.

Growth alone says little about value. Cost of sales in 2024 was RUB552.507 million, leaving RUB29.439 million of gross profit. Gross margin was therefore about 5.1%. Net profit was RUB19.393 million, equivalent to about 3.3% of revenue. A second registry-derived profile reports fixed assets of RUB173.9 million for 2024. This is a business with a material asset base and a narrow accounting margin, not a software-like operation in which infrastructure costs disappear inside high gross profit.

The figures do not reveal revenue composition. Property rent, equipment activity, technical work, intercompany charges and other sales can carry very different margins. Nor do they identify network expense. We cannot calculate return on AS207853 from the accounts. We can calculate how quickly an unjustified cost would consume earnings.

An annual cost equal to 0.5% of revenue would be about RUB2.91 million, or 15% of net profit. A cost equal to 1% of revenue would be RUB5.82 million, about 30% of net profit and nearly 20% of gross profit. Those are not estimates of the network budget. They are thresholds showing why "strategic" spending cannot be waved through without an avoided-loss case.

The direct RIPE charge is small. The 2026 charging scheme sets the annual contribution at EUR1,800 per LIR and an additional EUR50 per ASN assignment. Even allowing for banking friction and currency conversion, registry fees are unlikely to determine the economics of a company with more than half a billion rubles of revenue. The expensive layers are people, circuits, routing equipment, support, cybersecurity, power, spare parts and disciplined operations.

Capital refresh is particularly easy to defer. Routers and firewalls can remain functional after vendor support ends. Batteries can pass routine checks until they fail under load. Optics and line cards can be kept without a tested spare. This improves current cash but converts visible maintenance cost into hidden outage risk. An industrial operator with narrow margins may feel pressure to extend every asset's life; that is exactly when a written replacement schedule matters.

The network also competes with productive capital. RUB3 million can buy resilience, but it can also support building work, machine tooling, inventory, research or debt reduction. NPO Unimach should rank those uses on risk-adjusted return. A route that protects a high-value production commitment may outrank another machine. A route that duplicates the same physical duct may not outrank anything.

Revenue growth becomes value creation only if cash after maintenance and replacement rises. If the 12.7% increase came from asset utilisation at stable cost, it strengthens the ability to fund resilience. If it came from low-margin pass-through charges or related-party billing, it does not. The public accounts do not answer that question. The low gross margin makes the answer urgent.

Reliability has four payers and only one residual owner

Who pays for independence depends on contract design.

NPO Unimach can pay directly from its own margin. In that case the board should expect fewer losses, better supplier terms or chargeable service. Affiliated operating companies can pay through rent or network-service allocations. In that case the price should reflect usage and criticality, not become an arbitrary transfer. Outside tenants can pay a reliability premium inside rent or managed services, but only if the service is promised and measured. End buyers of industrial equipment can pay indirectly through product prices if dependable communications improve commissioning and support, although the current public material does not show AS207853 as part of a machine-service offer.

The beneficiaries are similarly divided. Industrial operators benefit if orders, engineering files and remote assistance remain reachable. Property users benefit if building and administrative services remain available. The owners benefit from lower interruption and bargaining risk. Upstream carriers benefit regardless of whether the protected business earns an adequate return, because contracted circuits generate revenue for them.

The downside is less evenly shared. NPO Unimach bears fixed registry and infrastructure obligations. A carrier bears only what its service agreement promises, often capped well below the customer's actual business loss. Equipment suppliers bear warranty obligations but not idle production. Staff and customers experience disruption, while the legal company carries missed revenue, penalties and recovery expense. Owners ultimately absorb the residual financial loss.

This asymmetry explains why redundancy is often underbought and badly priced. Each supplier can point to its own functioning component while the end-to-end service fails. Conversely, each internal beneficiary can treat connectivity as overhead and resist paying its share. The asset owner then either subsidises the network or cuts it until the next outage.

A rational allocation would connect price to service. A business needing thirty-minute recovery should pay more than one able to wait a day. A tenant consuming ordinary office access should not fund an industrial control requirement it does not use. A related company using public addresses and resilient hosting should contribute to router, security and transit costs. Transparent allocation does not create group cash, but it reveals which activities genuinely justify the infrastructure.

Without that allocation, AS207853 can support revenue growth while destroying company-level value. The network may be "important" to everyone and owned economically by no one. That is not independence; it is an unpriced common cost.

The cost base extends far beyond transit

Upstream connectivity is the visible recurring expense. NPO Unimach needs at least enough committed capacity for normal traffic and enough failover capacity for critical services. A cheap backup that cannot carry necessary traffic during a primary failure is not redundancy. A full-capacity second circuit is more valuable and more expensive. The optimal design depends on which services must survive and how quickly traffic can be reduced during an incident.

Equipment is the next layer. Dual external paths usually require at least two routing devices or an equivalent resilient design, separate power feeds, firewalls, switches, optics and out-of-band access. Capacity must include attack and failure scenarios, not only average use. Support contracts and spares matter because sanctions and supplier exits can lengthen replacement times. A spare that cannot run the current configuration is inventory, not resilience.

People are often the largest hidden cost. Someone must maintain route filters, contact data, domain records, address plans and access controls. Someone must test failover instead of assuming it. Someone must reconcile provider invoices, respond to incidents and keep documentation current. If the same small team operates AS207853 and AS207822, coordination can be efficient, but one staffing event can weaken both networks.

Security adds another fixed layer. Owning globally routed space expands the surface that must be monitored. Public services require patching, logging, access control and incident response. Route-security practices must prevent accidental leaks and unauthorised announcements. DDoS mitigation may be purchased from upstreams or a specialist, creating another supplier dependency. The absence of an attack in one year does not make the control unnecessary; it makes return difficult to observe.

Power and location can dominate all of the above. The same-building pattern is operationally efficient and economically concentrated. A site power event, fire, flood, access restriction or fibre cut at the entrance can defeat nominally separate carriers. Real independence may require an off-site service location, separate authoritative DNS, tested remote access and data replication. Those measures can cost more than the BGP layer itself.

Compliance is not merely a form. RIPE membership requires accurate holder and abuse contacts, annual payment and responsible resource administration. If NPO Unimach sells communications services, Russian licensing, service and security obligations would become a larger fixed cost. The public evidence does not establish that it does so, and the analysis should not impose operator economics on an enterprise network. The conditional point remains: monetising the network externally would add obligations before it added scale.

The cost base should therefore be divided into three columns: costs required for any ordinary enterprise connection; incremental costs caused by multihoming and resource ownership; and costs that would exist only if the company sold a service. Only the second column belongs in the independence decision. Only the third belongs in a connectivity growth case. Mixing them can make self-provisioning look either artificially cheap or unfairly expensive.

Upstream choice is real; upstream power remains

The visible carrier mix gives NPO Unimach options. AS44050 is a St Petersburg-focused provider. AS9049 belongs to a far larger network. AS207822 provides an affiliated route. Their different scale and ownership can reduce one-provider bargaining risk.

But NPO Unimach still buys reachability. It does not own a national backbone, international cable or major exchange fabric. Even direct peering would cover only selected destinations and would not replace full transit. The network's public visibility ultimately depends on larger carriers carrying its announcements and traffic.

Supplier concentration must be measured below the logo. Two carriers can lease fibre from the same infrastructure owner. They can meet at the same facility, use the same street route or depend on the same upstream outside St Petersburg. One may resell another's service. The public BGP view cannot reveal those common dependencies. Contracting three autonomous systems does not guarantee three physical supply chains.

The affiliated route introduces a different concentration. AS207822 is useful because it can coordinate closely and already hosts public brand services. That proximity may reduce transaction cost and speed repair. It may also share precisely the local risks that NPO Unimach most needs to diversify. An external carrier should protect against affiliated-network failure; the affiliated network should not be counted as fully independent until joint failure has been tested.

Carrier power also appears in pricing and support. NPO Unimach's small prefix estate gives it limited traffic volume compared with AS9049 or even AS44050. It is unlikely to dictate wholesale economics. Its leverage comes from being able to switch, not from buying at enormous scale. Portable addresses and active alternatives are therefore financially useful even if the network never expands.

The strongest supplier strategy would combine a focused local provider, a larger carrier and an affiliated emergency route, each with defined capacity and distinct physical access. It would test route withdrawal, equipment failure and building-power scenarios separately. The public topology is compatible with that strategy. Compatibility is not evidence that it has been achieved.

Customer concentration is hidden because the "customer" may be internal

A residential ISP can disclose subscribers and average revenue per line. NPO Unimach's likely network economics are harder. The main protected users may be a few companies, facilities or functions at one site. That creates concentration even if thousands of individual devices use the addresses.

The first concentration is geographic. The legal address, RIPE records and current machinery business all point to Kibalchicha Street. NPO Unimach also owns other property according to public reporting, but the network does not publish a site map. If most critical traffic enters one St Petersburg campus, one local incident can affect a large share of protected activity.

The second is corporate. AS207822, unimach.ru and the common ownership context point toward a small industrial grouping. If one affiliated operating company generates most demand, NPO Unimach's network return depends on that company's health and willingness to pay. An intercompany receivable can look like diversified service revenue only when the underlying cash comes from outside customers.

The third is commercial. Historical Unimach material named large industrial and state-linked buyers, while current material promotes shipbuilding, heavy industry and domestic manufacturing. Those markets can produce high-value orders and lumpy revenue. They can also make one contract, procurement decision or delayed acceptance disproportionately important. Because the current brand belongs publicly to NPK Morsvyazavtomatika, those customer claims cannot be assigned to NPO Unimach without legal-company evidence.

The fourth is application concentration. A small number of services may account for most outage cost: email, document exchange, remote maintenance, identity access, payment, or a production interface. Protecting those services may be cheaper through off-site hosting and replication than through making every local application highly available. The fact that unimach.ru web and mail already sit on AS207822 suggests at least some separation from AS207853, though not necessarily from the site or operating team.

NPO Unimach should disclose concentration in economic terms without exposing sensitive customers. The largest user share of network cost, largest site share of protected gross profit, largest application share of estimated outage loss and largest carrier share of committed capacity would be enough. Until those figures exist, the network may be protecting a diversified industrial base or one concentrated dependency. The valuation difference is substantial.

The realistic alternatives are cheaper and less autonomous

The relevant comparison is not between AS207853 and no Internet. It is between AS207853 and several managed alternatives.

The cheapest is a single enterprise circuit with provider-assigned addresses. It minimises engineering and equipment overhead. It is appropriate when interruption costs are low, renumbering is tolerable and the carrier has a strong local service record. For an industrial site with material digital dependence, it probably concentrates too much risk.

A stronger alternative is two managed circuits from separate carriers using provider addressing, with applications hosted in the cloud or behind managed failover. This can remove many single-carrier failures without direct LIR membership. It is easier to outsource but may complicate inbound services, VPN policies and address continuity. The company also relies on the integrator or carriers to make failover work.

A third option is colocation. NPO Unimach could place public services, security termination or a small routing presence in a carrier-neutral facility, connect the industrial site over two links and keep critical services away from local power and access risks. This improves physical diversity but adds facility, cross-connect and remote-support expense. It can be more efficient than duplicating a server room at the factory.

A fourth is to use AS207822 as the only group network and retire separate NPO Unimach routing. That would simplify operations and consolidate buying power. It would also place more control with the current brand operator and remove an independent resource-holder option. Whether consolidation saves more than it risks depends on cost allocation, ownership stability and the probability of needing to separate the companies later.

The fifth is the present multihomed model, improved with physical evidence and formal service economics. It preserves NPO Unimach's addressing, keeps carrier choice and can share resilience with AS207822. This is the most autonomous option, but autonomy is worth buying only when the cost of separation, outage or supplier pressure is high.

Competition therefore comes from managed service, not just other carriers. Cloud hosting, external email, content delivery, DDoS protection and managed security can move failure risk away from the local network. The current website and mail placement already demonstrate that not every public service needs to originate from AS207853. NPO Unimach should protect the business outcome, not maximise the number of functions it operates itself.

Regulation and geopolitics raise the value of control and its cost

NPO Unimach's network sits between Russian operations and a Dutch registry institution. RIPE says it continues to serve Russian members while complying with European Union sanctions. Its Russia and Ukraine guidance explains that Internet number registrations are treated as economic resources: a sanctioned holder's registration can be frozen against acquisition or transfer, while existing resources are not automatically deregistered and the membership agreement is not automatically terminated.

There is no basis here to say NPO Unimach is sanctioned. The relevant risk is procedural and financial. A Russian member depends on continuing due diligence, accurate legal identity, euro-denominated fees and workable payment channels. A false sanctions match or banking disruption can delay resource transactions even while routes continue to function. Owning resources protects against carrier renumbering but creates direct exposure to registry administration.

Technology supply is a larger issue. United States export controls on Russia cover broad classes of computers, telecommunications equipment, information-security products, lasers, sensors, industrial software and items used with computer-numerical-control machinery. The current US government summary emphasises due diligence and restrictions extending to re-exports and foreign-produced items with controlled technology. European Union measures have also expanded restrictions on high-technology and industrial goods.

The effect on NPO Unimach need not be an outright equipment shortage. It can appear as fewer authorised suppliers, indirect purchasing, longer lead times, reduced vendor support, software limitations, higher spare inventory and more engineering work to qualify substitutes. Those pressures touch both the industrial asset base and the network. A low-cost router is expensive if replacement takes months; an old supported configuration may be more valuable than a newer device with uncertain updates.

Domestic sourcing can reduce some exposure. The current Unimach site stresses Russian manufacturing and in-house production. That may support the economics of industrial equipment under import constraints. It does not make every network component domestic or interchangeable. The company should separate marketing claims about machine localisation from a bill-of-materials assessment for routing, security, optics, servers and power.

Regulation can also change the return on selling service. If NPO Unimach were to offer connectivity externally, licensing, lawful obligations, customer support and security requirements would add fixed cost. A compact enterprise network can be rational at the present scale; a small carrier operation may not be. The absence of public product evidence is therefore economically reassuring rather than a gap to fill. The company should not pursue telecom revenue merely because it owns telecom resources.

Geopolitics strengthens the case for optionality but weakens the case for excess complexity. Stable addresses, multiple suppliers and in-house knowledge reduce dependence. Too many unsupported vendors, informal import routes or fragile custom configurations increase it. Independence is not the number of suppliers on a diagram. It is the ability to restore service under realistic constraints.

Market signals show why uptime may command value, but not who captures it

Official company material describes Unimach machinery as reliable, locally supported and integrated into customers' operations. A 2024 Photonics article attributed more than 1,300 installed laser machines to the brand at that time and described a large production footprint. The current site raises the claimed installed count above 1,700. Again, these are brand and operating-company claims, not a disclosed NPO Unimach customer ledger. They still show the economic setting: expensive industrial equipment, service obligations and buyers for whom downtime matters.

Unofficial commentary makes the trade-off sharper. A long-running Chipmaker discussion includes users debating why Unimach equipment can cost more than Chinese alternatives, with comments pointing to component choices, local manufacturing, software and service. Another thread about a machine fault describes a production delay while remote diagnosis and service continued. A short Flamp review praised the machine but complained about waiting for repair.

These posts are self-selected, old in some cases and not verified. They cannot establish defect rates, service quality or current pricing. They are useful as market signals because they identify what customers debate: acquisition price, component origin, local service, downtime and repair speed. Those are precisely the variables through which reliable communications could matter to an industrial group.

A network can support remote diagnosis, parts identification, software distribution and service coordination. Faster communication may shorten repair time and strengthen a premium product position. But the connection is not automatic. A machine fault may require a technician and physical part regardless of network availability. A well-routed office network does not prove a well-run service operation. To claim value, the company would need data linking network availability to response time, remote resolution, avoided travel or customer retention.

The price debate is also instructive. Buyers may pay more for domestic accountability when imported alternatives carry uncertain support and parts. That premium belongs primarily to the machinery seller. NPO Unimach captures it only if its legal company receives product revenue or is paid for assets and services that make the promise credible. Shared owners do not solve this company-level question.

The market signal therefore supports the need for reliability but not the return to AS207853. Customers care about uptime. Public evidence does not show that they know about, contract for or pay NPO Unimach's routing capability. The economic bridge from network to revenue remains missing.

The facts that would change the judgment are measurable

The present conclusion can be overturned. NPO Unimach does not need to publish sensitive architecture or customer names. It needs to publish or internally govern a compact set of measures.

First, define the operating boundary. Identify which legal company owns routers, pays RIPE and carrier bills, employs or contracts network staff, and receives service charges. State whether AS207853 serves only NPO Unimach, common facilities, affiliated companies, outside tenants or paying communications customers. This is the foundation for every return calculation.

Second, show route independence in physical terms. Count carrier entrances, facility terminations, router failure domains and power sources. Record quarterly failover tests and the capacity available after each simulated failure. Report correlated outage minutes separately from single-carrier outage minutes. Three BGP neighbours would become strong evidence if the paths survive independent tests.

Third, calculate the annual incremental cost of independence. Include the extra circuits, LIR and resource charges, routing and security equipment, support, power, colocation, spares, staff time and outside services that would disappear under the best managed alternative. Do not charge ordinary corporate IT to the decision merely because AS207853 exists.

Fourth, quantify avoided loss. For each critical function, estimate gross profit, contractual penalty, idle labour, recovery cost and customer consequence per hour. Multiply by outage probability and the reduction achieved by the independent design. Use conservative assumptions and compare them with actual incidents. A low-frequency event can justify investment, but only when its impact is credible.

Fifth, reconcile financial growth. Explain the RUB65.663 million revenue increase between 2023 and 2024, the 5.1% gross margin and the role of property, industrial activity, research and intercompany services. Disclose connectivity or tenant-service revenue if it exists. Revenue attached to low-margin pass-through services should not be confused with value creation.

Sixth, disclose concentration without names. Show the largest affiliated user, outside customer, site, application and carrier shares of cost or protected contribution. If one company receives most of the benefit, put a durable service agreement behind it. If one site carries most of the risk, test an off-site alternative.

Seventh, publish outcome measures: network availability, mean time to restore, successful remote-service sessions, security incidents, route leaks, DDoS events and emergency changes. A board should be able to see whether reliability improved after each capital decision. Engineering activity is not the outcome.

Any one of three findings would materially improve the judgment: independently routed and powered paths with tested failover; annual avoided losses comfortably above incremental network cost; or recurring external and intercompany service revenue with positive contribution after replacement capital. None is visible today.

The verdict: keep the option, refuse the growth story

NPO Unimach has built more network control than a normal single-carrier industrial customer. The active ASN, IPv4 block, two IPv6 resources, three observed neighbours and coordinated backup relationship with AS207822 form a credible continuity asset. The structure can preserve addressing, improve carrier bargaining power and reduce selected outage risks.

It has not publicly proved independence in the sense that matters. The commercial web and mail presence depends on the affiliated AS207822. The networks share a site and ownership context. Physical route, power and staff diversity are undisclosed. There is no PeeringDB record for AS207853, no observed downstream autonomous system and no public connectivity offer. The legal company's main registered activity is property, while the current machinery brand belongs operationally to another company.

The financial test is severe. A 3.3% net margin means that poorly measured resilience can consume value quickly. The RIPE fee is not the problem; circuits, people, security and refresh are. NPO Unimach should keep the resource option if it can demonstrate tested path diversity and avoided loss. It should consolidate or outsource parts of the design if a managed dual-carrier service protects the same cash flows for less.

The explicit conclusion is that AS207853 is presently an insurance asset, not a telecom growth business. Customers may value local accountability and reliable industrial support, but public evidence does not show that they pay NPO Unimach enough for network independence to cover its full economic cost. Until cost allocation, physical diversity and outage economics are disclosed, claims of strategic autonomy amount to capability, not value creation.