The discrepancy between personal-attribution sources and official ASN records creates a risk of false operator identification. Until resolved, analysts who treat Likhacev as the network owner could misdirect operational activities such as monitoring, routing security checks, or incident handling.
AuthorLydia Luo
Editorial owner accountable for this profile route.
Reading Time2 min
Estimated reading time at standard editorial pace.
PublishedJun 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.
RegionGlobal
Primary geography where current signals are most visible.
Signal FocusInstitution Type
Principal area tracked in this intelligence profile.
Content TypeProfile
Structured profile used for cross-category comparison.
Primary DomainInfrastructure
Primary editorial domain framing the analysis.
TopicPublic network contact
Controlled taxonomy label used for this profile route.
Time HorizonQuarter (30-120d)
Most likely window for material strategy effects.
ImpactMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
Confidence0.95
Anchored to multiple primary-source references and direct disclosures.
Evidence Pack
Primary-source references used for classification and impact scoring.
Arseniy Likhacev is a routing-context name without verified employment or biographical details. Public evidence links the name to AS214745 and one IPv6 prefix, but official ASN records point to Vexelia Ltd, creating an unresolved attribution conflict. The profile is provisional: without a current RIPE handle or operator-published page, the identity as a network operator cannot be confirmed. Watchpoints include direct WHOIS resolution, BGP activity, and official documentation from Vexelia Ltd.
Core Entity Brief
Core Entity Brief
Entity
Arseniy Likhacev
Public role
The discrepancy between personal-attribution sources and official ASN records creates a risk of false operator identification. Until resolved, analysts who treat Likhacev as the network owner could misdirect operational activities such as monitoring, routing security checks, or incident 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
Arseniy Likhacev is presented as a Individual registry-holder label in the BTW company and institution directory. The discrepancy between personal-attribution sources and official ASN records creates a risk of false operator identification. Until resolved, analysts who treat Likhacev as the network owner could misdirect operational activities such as monitoring, routing security checks, or incident handling.
The current public read is bounded by primary domain: Infrastructure; signal focus: Institution Type; time horizon: Quarter (30-120d); impact band: Medium. These fields give readers a stable baseline for comparing the profile with other institutions, operators, and market actors.
The evidence basis currently includes 7 public evidence references and the linked public profile. Claims should stay limited to role, context, operating surface, dependencies, and watchpoints that are visible in reviewed public material.
Domain of operation
The discrepancy between personal-attribution sources and official ASN records creates a risk of false operator identification. Until resolved, analysts who treat Likhacev as the network owner could misdirect operational activities such as monitoring, routing security checks, or incident handling.
Public role: Arseniy Likhacev is framed by the discrepancy between personal-attribution sources and official asn records creates a risk of false operator identification. until resolved, analysts who treat likhacev as the network owner could misdirect operational activities such as monitoring, routing security checks, or incident handling. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record; radar.cloudflare.com
Operating surface: Public network contact and Global provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record; radar.cloudflare.com
Timeline
Arseniy Likhacev public profile updated
Public coverage records Arseniy Likhacev as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: The discrepancy between personal-attribution sources and official ASN records creates a risk of false operator identification. Until resolved, analysts who treat Likhacev as the network owner could misdirect operational activities such as monitoring, routing security checks, or incident handling.
Object role: The name appears in IRR remarks, prefix lookups, and personal ASN tags, suggesting a routing-related role. However, no verified job title, employer, or RIPE handle confirms an active operator position, so the subject should be treated as an unresolved routing-contact attribution rather than a confirmed network operator.
Impact note: If the person controls AS214745, changes in BGP announcements could affect networks relying on routes via AS207567 or AS213449. The more immediate impact is misattribution risk: misidentifying the operator could lead to misguided security responses or resource-tracing errors.
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 Arseniy Likhacev 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 Arseniy Likhacev included?
Arseniy Likhacev 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.
