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.
AuteurSummer Ren
Editorial owner accountable for this profile route.
Temps de lecture2 min
Estimated reading time at standard editorial pace.
Publié leJun 02, 2026
Date this profile last entered editorial circulation.
Last updateJun 02, 2026
Date this profile last entered editorial circulation.
CategoryIndividual registry-holder label
Controlled classification used for cross-profile comparison.
RégionGlobal
Primary geography where current signals are most visible.
Signal FocusInstitution Type
Principal area tracked in this intelligence profile.
Type de contenuProfile
Structured profile used for cross-category comparison.
Domaine principalInfrastructure
Primary editorial domain framing the analysis.
SujetPublic network contact
Controlled taxonomy label used for this profile route.
HorizonQuarter (30-120d)
Most likely window for material strategy effects.
ImpactMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
Confiance0.95
Anchored to multiple primary-source references and direct disclosures.
Dossier de preuves
Sources primaires utilisées pour la classification et l'évaluation d'impact.
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.
Core Entity Brief
Core Entity Brief
Entity
Sharenkov Alexey
Public role
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.
Region
Global
Category
Individual registry-holder label
Primary domain
Infrastructure
Signal focus
Institution Type
Time horizon
Quarter (30-120d)
Impact
Medium
Confidence
0.95
Evidence coverage
7 public source references
Related coverage
Profile anchor article
Website
Public evidence pending
Last update
Jun 02, 2026
Sharenkov Alexey is a registry-holder label for AS200467 and associated IP prefixes, material only as a public network-contact surface with no verified commercial operation.
What It Does
Registry contact role: Serves as the named technical and administrative contact in RIPE WHOIS for Sharenkov‑branded network records, enabling registry modifications and follow‑up accountability.
Revenue and customer gap: No public evidence establishes a revenue model, customer base, or commercial service; claims of a business entity require official or financial documentation.
Operating Snapshot
Registry identity baseline: External sources identify the label with AS200467 and prefix ranges 5.59.222.0/24 and 5.59.223.0/24, all registered under RIPE.
Routing context: bgp.tools shows three originated IPv4 /24s with upstreams Miranda‑Media Ltd, CRELCOM LLC, and Uzhnie Magistraljnie Linii Svyazi LLC; no IPv6 announcements observed.
Control Surface
Numbering records: RIPE person handles SHAR3‑RIPE and SHAR4‑RIPE, organisation records ORG‑SHAR4‑RIPE and ORG‑SHAR8‑RIPE, and associated aut‑num and inetnum objects.
Evidence‑triggered changes: New prefix announcements, upstream shifts, or handle reassignments can alter the operational significance of the Sharenkov label.
Watchpoints
Record freshness: Stale or conflicting public registry records are the primary uncertainty; the assessment depends on accurate live RIPE data.
Footprint expansion: A corporate website, PeeringDB entry, or new ASN registration would materially increase the subject's infrastructure relevance.
Domain of operation
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.
Public role: Sharenkov Alexey is framed by 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. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record; Registry RDAP / WHOIS record
Operating surface: Public network contact and Global provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record; Registry RDAP / WHOIS record
Timeline
Sharenkov Alexey public profile updated
Public coverage records Sharenkov Alexey as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: 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.
Object role: 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.
Impact note: 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.
Control surface: public operating records, official service pages, source-backed relationship updates
Key dependencies: official company sources, public registries, operator-published records
Public View
The public read of Sharenkov Alexey is limited to visible role, operating context, and relationship evidence.
Watchpoints
New public role, affiliation, product, policy, or market disclosures.
Verified relationship changes involving named organizations or people.
Caveats
Private or unverified claims are excluded from this public view.
FAQ
Why is Sharenkov Alexey included?
Sharenkov Alexey has public evidence that makes the institution relevant to BTW's coverage of digital infrastructure, governance, or markets.
What is public about this profile?
The public layer covers visible role, operating context, linked organizations, and evidence-backed watchpoints.
What should readers watch next?
Readers should watch for source-backed role changes, new partnerships, regulatory exposure, operating expansion, or evidence that changes the public assessment.
