Vyacheslav Nikolaevich Nerushenko

Vyacheslav Nikolaevich Nerushenko is listed as the holder of AS211860 in RIPE NCC registry records with no announced prefixes. The profile documents the registry contact role, the absent routing footprint, and principal uncertainties: lack of commercial context, unknown location, and unverified operational activity. Watchpoints include first prefix announcement and registry record changes. Evidence is limited to three public RIPE/RDAP sources; no corporate, PeeringDB, or service data supports a broader claim.

Vyacheslav Nikolaevich Nerushenko

Vyacheslav Nikolaevich Nerushenko holds the dormant autonomous system AS211860, registered in the RIPE NCC with no active prefixes. This profile establishes a reference point for a potential routing actor; any activation or registry change would introduce new interconnection dynamics requiring immediate assessment.

Why It Matters

If AS211860 begins announcing prefixes, engineers would need to identify upstream peers, potential traffic paths, and the security posture of the new entrant. A change in registry holder could signify a behind-the-scenes asset sale, shifting control without public notice. Either scenario could ripple through interconnection agreements and routing security policies.

What Public Sources Show

Vyacheslav Nikolaevich Nerushenko is the holder of dormant autonomous system AS211860 in the RIPE NCC registry. The ASN announces no prefixes, remaining invisible to global routing. Yet the registration grants him administrative and technical control, creating a latent dependency. A single prefix announcement would introduce a new actor with no operational history for engineers to review.

Public evidence is limited to three official sources. A RIPE NCC AS-overview query confirms the holder name and AS name 'VPSDEDIC-AS.' An RDAP lookup provides identical data, while a RIPEstat query returns zero active prefixes. No corporate website, PeeringDB entry, or additional resources are associated with him. The registration is the sole touchpoint between Nerushenko and public Internet infrastructure records.

The entire control surface is the RIPE NCC database entry for AS211860. As administrative and technical contact, Nerushenko can update contacts, request changes, and originate BGP announcements. There is no external corporate structure, operational network, or financial backing governing this authority. The only barrier between dormancy and activation is the holder's own decision.

If AS211860 begins announcing prefixes, operators would need to identify upstream peers, evaluate traffic paths, and assess the new entrant's security posture. A registry holder change could signal an asset sale without public notice. Either scenario could ripple through interconnection agreements and routing security policies, as a previously absent party suddenly participates in global routing.

Analysts should track three watchpoints: first, any RDAP or WHOIS record modification for AS211860 signaling a transfer of control; second, the initial BGP prefix announcement ending the ASN's dormancy; third, the emergence of a company registration, website, or PeeringDB profile linking Nerushenko to a formal business, which would clarify intent and operational posture.

Key gaps persist. Nerushenko's location, background, and network affiliations are unknown. No commercial services or contracts are tied to the ASN. Registration history details are absent from current evidence. All conclusions rest on the accuracy of RIPE NCC data. The dormant state could be deliberate or incidental; we cannot determine motive from available records.

The profile relies on three public registry sources: the RIPE NCC AS-overview API, an RDAP lookup for AS211860, and the RIPEstat announced-prefixes query. They provide a narrow but sufficient foundation for monitoring this latent routing dependency.

Operating Surface

As the administrative and technical contact for AS211860, he holds the authority to manage routing announcements, update registration data, and request resource changes; no active routing or commercial service is documented, making the role currently limited to a registry contact.

The subject matters because a future change—a first prefix announcement, a transfer of the holder, or the appearance of commercial infrastructure—would inject a previously absent actor into the global routing fabric. Establishing a baseline now allows analysts to quickly assess the significance of such events and the escalation pathways they create.

Watchpoints

AS211860 represents a dormant but registered Autonomous System under individual control. Its activation would introduce an unvetted actor into the global routing table, potentially creating new traffic paths or interconnection obligations that currently do not exist. Monitoring the passive registry entry serves as an early-warning mechanism for a sudden shift in the routing landscape.

Monitor for first BGP announcements, registry record changes, and any corporate linkage that would convert the personal registry contact into an operational network operator.

No corporate registration, operational network footprint, or historical routing data exists. The subject's location, background, and network affiliations are unknown, limiting any assessment of capability or intent.

Sources

• RIPE NCC AS Overview - AS211860 is registered to Vyacheslav Nikolaevich Nerushenko with AS name 'VPSDEDIC-AS' and no announced prefixes.
• RDAP Record for AS211860 - Confirms the holder and contact details for AS211860.
• RIPEstat Announced Prefixes - No IPv4 or IPv6 prefixes are currently announced by AS211860.