RZDZDOR JSC RZD-Zdorovie is a Russian-registered ASN holder with no active routing presence. The entity’s public footprint is confined to RIPE NCC records; there is no evidence of commercial operations, customers, or network services. Its significance is prospective: any registry change or prefix announcement would shift it from dormant stub to active network participant, warranting monitoring. Current data gaps include corporate website, leadership, and revenue model. The profile is built from three registry sources and should be updated if any new signals emerge.
The entity’s public role is confined to administrative stewardship of AS211616. It does not operate any networks visible in the global BGP table, nor does it provide transit, peering, or connectivity services. The registration itself is the sole public function; there is no evidence of a commercial business, customers, or technical infrastructure.
An apparently dormant ASN holder in the Russian numbering space merits monitoring because any registry change—such as a new prefix announcement, contact update, or transfer—could signal the activation of a previously unseen network. Such an event would have implications for regional routing topology, dependency analysis, and security assessment for operators tracking Russian internet infrastructure.
An apparently dormant ASN holder in the Russian numbering space merits monitoring because any registry change—such as a new prefix announcement, contact update, or transfer—could signal the activation of a previously unseen network. Such an event would have implications for regional routing topology, dependency analysis, and security assessment for operators tracking Russian internet infrastructure.
The entity’s public role is confined to administrative stewardship of AS211616. It does not operate any networks visible in the global BGP table, nor does it provide transit, peering, or connectivity services. The registration itself is the sole public function; there is no evidence of a commercial business, customers, or technical infrastructure.
If RZDZDOR JSC RZD-Zdorovie begins advertising IP prefixes, it would shift from a dormant registry entry to an active network participant. This could introduce new routing dependencies, transit paths, or risk vectors in the Russian internet ecosystem, requiring routing security analysts to evaluate its trustworthiness, interconnectivity, and potential for abuse.
RZDZDOR JSC RZD-Zdorovie is a Russian-registered ASN holder with no active routing presence. The entity’s public footprint is confined to RIPE NCC records; there is no evidence of commercial operations, customers, or network services. Its significance is prospective: any registry change or prefix announcement would shift it from dormant stub to active network participant, warranting monitoring. Current data gaps include corporate website, leadership, and revenue model. The profile is built from three registry sources and should be updated if any new signals emerge.
If RZDZDOR JSC RZD-Zdorovie begins advertising IP prefixes, it would shift from a dormant registry entry to an active network participant. This could introduce new routing dependencies, transit paths, or risk vectors in the Russian internet ecosystem, requiring routing security analysts to evaluate its trustworthiness, interconnectivity, and potential for abuse.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
RZDZDOR JSC RZD-Zdorovie
RZDZDOR JSC RZD-Zdorovie is a Russian company registered as the holder of Autonomous System AS211616 in the RIPE NCC database. Despite holding the ASN since at least 2021, it announces no IP prefixes and has no visible network operations, website, or commercial services. Its significance is entirely prospective: any registry change or prefix announcement would convert a dormant stub into an active internet participant warranting security and routing analysis.
Why It Matters
If RZDZDOR JSC RZD-Zdorovie begins advertising IP prefixes, it would shift from a dormant registry entry to an active network participant. This could introduce new routing dependencies, transit paths, or risk vectors in the Russian internet ecosystem, requiring routing security analysts to evaluate its trustworthiness, interconnectivity, and potential for abuse. See also: Tim Zuidema trading as TiZu.
What Public Sources Show
RZDZDOR JSC RZD-Zdorovie appears in the RIPE NCC registry as the holder of Autonomous System AS211616, a Russian number resource. Despite having held the ASN since at least 2021, the entity does not announce any IP prefixes into the global routing table. This means it has no active role in internet routing and contributes no connectivity or transit services. See also: HIPERNET TELEKOMUNIKASYON.
Its public footprint ends at the registry record; no website, PeeringDB entry, or customer-facing service pages have been located.
The absence of active routing makes RZDZDOR JSC RZD-Zdorovie a dormant stub in the Russian internet ecosystem. However, the registration itself is a live administrative entry. Any future change—a prefix announcement, an updated contact, or a transfer of the ASN—would convert it into an active network participant. For routing analysts and security researchers, such a shift could introduce new dependencies, transit paths, or points of trust that require assessment.
Public evidence is limited to three official registry sources. A RIPEstat AS overview confirms the assignment of AS211616 to RZDZDOR JSC RZD-Zdorovie with country code RU. An RDAP lookup shows the ASN was registered in 2021 and lacks associated routes. A check of announced prefixes via RIPEstat returns zero results, confirming the absence of announced IPv4 or IPv6 prefixes.
No independent corporate website, press release, or commercial profile supplements these registry records.
The observable operating surface is narrow. The company’s sole verifiable control point is the AS211616 registry record in the RIPE NCC database. Administrative actions such as modifying the holder name, updating contacts, or recording a status change are the only publicly visible activities. There is no evidence of network equipment, colocation, peering agreements, or customer contracts.
Should the company possess or acquire IP address blocks, it could begin originating routes, fundamentally altering its surface.
Monitoring this entity requires tracking three signals. First, any alteration to the AS211616 registry entry—especially a new holder or contact email—may indicate an organisational reactivation or sale. Second, the detection of any BGP announcement from AS211616, however small, would transition it from dormant to live, demanding immediate routing security review.
Third, the emergence of an official website, a PeeringDB page, or a business registration under the RZDZDOR name would fill current knowledge gaps.
Substantial unknowns surround the company. Its commercial purpose, if any, is not documented. There is no public information about its leadership, staffing, or technical authority. The physical location is unverified beyond the RU country tag. The entity could be a holding company, a pre-operational vehicle, or a legacy registration with no future plans. Until observable signals change, the public profile remains a registry stub.
Operating Surface
The entity’s public role is confined to administrative stewardship of AS211616. It does not operate any networks visible in the global BGP table, nor does it provide transit, peering, or connectivity services. The registration itself is the sole public function; there is no evidence of a commercial business, customers, or technical infrastructure.
An apparently dormant ASN holder in the Russian numbering space merits monitoring because any registry change—such as a new prefix announcement, contact update, or transfer—could signal the activation of a previously unseen network. Such an event would have implications for regional routing topology, dependency analysis, and security assessment for operators tracking Russian internet infrastructure.
Watchpoints
The entity is a dormant registry stub. Its presence alone does not warrant urgent action, but its potential activation makes it a monitoring target. If it begins routing, it could represent a new Russian network operator with unknown commercial or state ties.
Watch for any change in the RIPE NCC registry for AS211616, including new contact handles or organization name changes. Also monitor BGP feeds for any prefix announcements from AS211616. The appearance of corporate infrastructure like a website or PeeringDB entry would reduce uncertainty.
No first-party website or service description exists. The commercial business model, leadership, and physical location are unknown. Collecting Russian corporate registries, director filings, or business license data could clarify the entity's nature.
Sources
- Internet registry record - public-source identity and registry context for RZDZDOR JSC RZD-Zdorovie.
- Registry RDAP / WHOIS record - evidence-led registry, routing, or network context for RZDZDOR JSC RZD-Zdorovie.
- Internet registry record - evidence-led routing visibility context for RZDZDOR JSC RZD-Zdorovie via AS211616.
Domain of operation
RZDZDOR JSC RZD-Zdorovie is a Russian company registered as the holder of Autonomous System AS211616 in the RIPE NCC database. Despite holding the ASN since at least 2021, it announces no IP prefixes and has no visible network operations, website, or commercial services. Its significance is entirely prospective: any registry change or prefix announcement would convert a dormant stub into an active internet participant warranting security and routing analysis.
- Internet registry record: public-source identity and registry context for RZDZDOR JSC RZD-Zdorovie. Evidence basis: source-a14e199a26dd
Timeline
- RZDZDOR JSC RZD-Zdorovie public evidence observed
An apparently dormant ASN holder in the Russian numbering space merits monitoring because any registry change—such as a new prefix announcement, contact update, or transfer—could signal the activation of a previously unseen network. Such an event would have implications for regional routing topology, dependency analysis, and security assessment for operators tracking Russian internet infrastructure.
At A Glance
- Name: RZDZDOR JSC RZD-Zdorovie
- Type: Network infrastructure operator
- Base: RU
- Profile focus: Company
What It Does
- public operating records
- official service pages
- documented relationships updates
Why It Matters
- If RZDZDOR JSC RZD-Zdorovie begins advertising IP prefixes, it would shift from a dormant registry entry to an active network participant. This could introduce new routing dependencies, transit paths, or risk vectors in the Russian internet ecosystem, requiring routing security analysts to evaluate its trustworthiness, interconnectivity, and potential for abuse.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
If RZDZDOR JSC RZD-Zdorovie begins advertising IP prefixes, it would shift from a dormant registry entry to an active network participant. This could introduce new routing dependencies, transit paths, or risk vectors in the Russian internet ecosystem, requiring routing security analysts to evaluate its trustworthiness, interconnectivity, and potential for abuse.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
If RZDZDOR JSC RZD-Zdorovie begins advertising IP prefixes, it would shift from a dormant registry entry to an active network participant. This could introduce new routing dependencies, transit paths, or risk vectors in the Russian internet ecosystem, requiring routing security analysts to evaluate its trustworthiness, interconnectivity, and potential for abuse.
Watchpoints
- The entity is a dormant registry stub.
- Its presence alone does not warrant urgent action, but its potential activation makes it a monitoring target.
- If it begins routing, it could represent a new Russian network operator with unknown commercial or state ties.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track RZDZDOR JSC RZD-Zdorovie?
An apparently dormant ASN holder in the Russian numbering space merits monitoring because any registry change—such as a new prefix announcement, contact update, or transfer—could signal the activation of a previously unseen network. Such an event would have implications for regional routing topology, dependency analysis, and security assessment for operators tracking Russian internet infrastructure.
What evidence supports the profile?
public-source identity and registry context for RZDZDOR JSC RZD-Zdorovie.
What should readers watch next?
The entity is a dormant registry stub.
