Sharenkov Alexey is a RIPE registry contact tied to AS200467 and Sharenkov‑branded IP prefixes. Public routing mirrors and WHOIS data confirm his admin‑c and tech‑c role, providing a point of accountability for those resources. The profile is limited to registry evidence: no employer, job title, or commercial service is verified. Conflicting data for AS215550 requires direct RIPE reconciliation. Watchpoints include handle continuity, prefix count changes, and appearance of corporate identifiers. The assessment will change if official records resolve the handle variants or the AS215550 dispute.

Sharenkov Alexey

Sharenkov Alexey is a publicly visible RIPE registry contact associated with autonomous system AS200467 and Sharenkov‑branded IP prefixes. Public WHOIS mirrors and routing data confirm his administrative and technical role for those resources, providing a follow‑up surface for routing and abuse inquiries, though no employer, job title, or commercial service is verified. The assessment is limited to registry accountability.

Why It Matters

If Sharenkov modifies his RIPE handles, the associated aut‑num or prefix records could change without notice, affecting routing observability and abuse contact paths. Conversely, the appearance of a corporate affiliation or expanded prefix set would elevate the subject's infrastructure significance.

What Public Sources Show

Sharenkov Alexey is a publicly visible contact in the RIPE network registry, listed as the administrative and technical handler for autonomous system AS200467 and several IP prefix blocks bearing the Sharenkov label. Public WHOIS mirrors and routing intelligence services confirm his role, but no employment details or corporate affiliation beyond the registry have been verified. His public identity is thus a registry accountability surface, not a commercial or biographical profile.

The subject matters because his registry handle continuity helps network analysts track who is responsible for routing reachability, abuse contact, and resource maintenance for these assets. A change in his handle assignments, the set of announced prefixes, or upstream network peers can signal resource transfers, routing-policy shifts, or reconciliation errors that require investigation. Monitoring these signals supports early detection of operational or ownership changes.

Public sources, including RIPE WHOIS mirrors and routing platforms such as bgp.tools and IPinfo, identify AS200467 as SHARENKOV, with organisation ORG-SHAR4-RIPE and person object Sharenkov Alexey Ivanovich handling admin‑c and tech‑c duties via handle SHAR3‑RIPE. The autonomous system originates three IPv4 /24 prefixes, and its observed upstreams are Miranda‑Media Ltd, CRELCOM LLC, and Uzhnie Magistraljnie Linii Svyazi LLC.

The visible operating surface is confined to registry and routing administration. Sharenkov’s authority lies in his ability to modify RIPE objects—aut‑num records, inetnum records, route objects, and maintainer references—through the associated person handles. This does not imply a broader corporate title or private network‑management role. The AS215550 linkage is contested: Hurricane Electric shows Athorio GmbH, while Ultralir associates it with the Sharenkov label; the conflict remains unresolved.

If Sharenkov withdraws or reassigns prefixes, changes upstreams, or alters registry details, routing observability and abuse‑contact paths for the associated IP space could shift without public notice. Conversely, the appearance of a corporate website, PeeringDB entry, or disclosed employer would materially elevate the subject’s operational significance. The impact mechanism is therefore entirely one of registry‑based reachability and accountability.

Key watchpoints include: live RIPE verification that SHAR3‑RIPE and SHAR4‑RIPE still control the same resources; prefix‑count stability for AS200467; any change in upstream peers; and official reconciliation of the AS215550 conflict between the Sharenkov and Athorio identities. A new handle appearing on additional ASNs or prefixes would also warrant immediate re‑assessment.

Significant uncertainty remains. Multiple handle variants—Sharenkov Alexey, Sharenkov Alexey Ivanovich, Oleksii Sharienkov—and organisation identifiers ORG‑SHAR4‑RIPE and ORG‑SHAR8‑RIPE coexist without public confirmation of identity alignment. No biographic, employer, or service‑description source has been reviewed. Until official RIPE data or corporate disclosure resolves these variants, the profile must be read strictly as a registry‑contact surveillance note.

Operating Surface

He serves as the public administrative and technical contact for RIPE‑registered network resources branded under the Sharenkov label, including AS200467 and the IP Sharenkov Alexey prefix blocks. This role grants authority to modify registry records and route objects, making him the visible point of control for those resources.

Changes in his handle assignments, prefix origins, or upstream peers can signal resource transfers, policy shifts, or reconciliation problems that require investigation. Registry continuity helps analysts identify who is publicly accountable for routing reachability and abuse handling.

Watchpoints

The subject operates as a registry‑only contact surface. His public network footprint is modest, and no corporate persona is established. Intelligence value lies in monitoring handle continuity and routing changes, not in attributing broader network control.

Changes in RIPE handle assignments, prefix announcements, upstream peers, or the appearance of corporate identifiers (website, PeeringDB) would raise the subject's significance. The AS215550 conflict is a crucial reconciliation point.

Direct RIPE live data is needed to confirm handle linkages and resolve the AS215550 conflict. No employer, website, or service description is available. Biography and commercial context remain absent from public sources.

Sources

• Registry RDAP / WHOIS record - A public RDAP query for AS215550 provides identity and registry context for Sharenkov Alexey.
• Registry RDAP / WHOIS record - RIPE-derived WHOIS for AS200467 displayed by 2ip.io identifies the aut-num as SHARENKOV, with organisation ORG-SHAR4-RIPE, sponsor ORG-Vs35-RIPE, admin-c and tech-c SHAR3-RIPE, and a person object named Sharenkov Alexey Ivanovich.
• bgp.tools - bgp.tools identifies AS200467 as Oleksii Sharienkov, registered to ORG-SHAR4-RIPE, active under RIPE, with three originated IPv4 /24 prefixes and upstreams Miranda-Media Ltd, CRELCOM LLC, and Uzhnie Magistraljnie Linii Svyazi LLC.
• ipinfo.io - IPinfo records AS200467 as Oleksii Sharienkov in Ukraine, allocated on 2022-12-16, with an IP range labeled 'IP Sharenkov Alexey'.
• ipinfo.io - An IPinfo prefix page for 5.59.223.0/24 shows a RIPE inetnum named Sharenkov, description 'IP Sharenkov Alexey', organisation ORG-SHAR8-RIPE, and admin‑c and tech‑c handle SHAR4-RIPE.
• bgp.he.net - Hurricane Electric's BGP Toolkit identifies AS215550 as Athorio GmbH, conflicting with the Sharenkov association.
• ultralir.com - Ultralir's Vissado inventory lists AS215550 as 'ASSHARENKOV' with owner ORG-SHAR8-RIPE, indicating that the AS215550 identity is a reconciliation watchpoint.