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.

Arseniy Likhacev

Arseniy Likhacev is a routing-context name linked to AS214745 and one IPv6 prefix, but official registry records identify Vexelia Ltd as the holder, creating an unresolved attribution conflict that matters for network monitoring and incident response.

Why It Matters

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.

What Public Sources Show

Arseniy Likhacev is a name that surfaces in public routing datasets tied to autonomous system AS214745 and the IPv6 prefix 2a10:ab80:3e5::/48. The official registry holder for AS214745, however, is the United Kingdom-based company Vexelia Ltd. This unresolved conflict makes it impossible to confirm whether Likhacev exercises operational control over the network resources, turning the profile into a study of attribution risk rather than a settled operator biography.

Several public sources embed the name in network context. BigDataCloud’s prefix lookup associates 2a10:ab80:3e5::/48 directly with “ARSENIY-LIKHACHEV” and lists AS214745 as the carrier. Hurricane Electric’s IRR records include a remark naming Arseniy Likhacev alongside AS214745 within AS-set AS213449:AS-JOW. The bgp.tools personal ASN tag page also lists the name, although the direct AS214745 page could not be retrieved.

In contrast, Cloudflare Radar and IPinfo both identify AS214745 as belonging to Vexelia Ltd, registered in the United Kingdom with the website vexelia.com.

This split in the public record means the network’s identity is ambiguous. AS214745 could be a personal project operated under a corporate registration, or the Likhacev name might be a legacy contact, a routing artifact, or a simple data-entry error.

No verified RIPE handle, employment record, or published biography ties Arseniy Likhacev unequivocally to an operational role for Vexelia Ltd or any other organisation, leaving the person’s actual authority open to question.

If Likhacev were the de facto operator, the control surface would include BGP route origination, management of the /48 prefix, and relationships with upstream provider AS207567 and the neighbouring AS213449. In practice, because the control assertion is unverified, any analysis that treats Likhacev as the network’s owner must be cross-checked against the official RIPE registration and real-time routing activity.

The impact mechanism is straightforward: changes in AS214745’s announcements could affect any network that accepts routes from AS207567 or AS213449. For analysts monitoring the region, the more immediate danger is misattribution—assigning authority to the wrong name could misdirect incident response, resource tracking, or threat assessment.

Watchpoints that would raise confidence in the profile include a direct RIPE WHOIS resolution for AS214745 showing Likhacev as a technical or administrative contact, any BGP announcement or withdrawal originated by the AS, official documentation from Vexelia Ltd referencing the individual, or a PeeringDB entry that links the name to an active network role.

Conversely, if Vexelia Ltd remains the sole public holder without any mention of Likhacev in operational channels, the personal attribution from routing-index sites should be treated as unreliable.

Spelling variations add another layer of caution. The name appears as both “Likhacev” and “Likhachev” in public results, and a separate academic thesis from HSE University names an Arseniy Likhachev with no demonstrated link to AS214745. Until an authoritative source confirms the person’s relationship to the network, any profile of Arseniy Likhacev must remain provisional.

Operating Surface

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.

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.

Watchpoints

The conflict between personal-attribution sources and official registry data makes this subject a marker for attribution hygiene rather than a concrete operator profile. Until the discrepancy is resolved, any operational significance assigned to the name is speculative and carries risk of misdirection.

Direct RIPE WHOIS query for AS214745; any BGP announcement or withdrawal from the AS; official Vexelia Ltd documentation naming Likhacev; PeeringDB entry linking the name to an active role.

No verified RIPE handle, no employer or biography tied to the network, spelling variations unresolved, no active BGP sample in current evidence set.

Sources

• Registry RDAP / WHOIS record - Public-source identity and registry context for Arseniy Likhacev.
• radar.cloudflare.com - Cloudflare Radar identifies AS214745 as VEXELIA-AS, alias Vexelia, country United Kingdom, with website https://www.vexelia.com.
• ipinfo.io - IPinfo identifies AS214745 as Vexelia Ltd in the United Kingdom, registry RIPE, allocated June 7, 2024 and updated August 26, 2025, with no IPv4 or IPv6 address space in its summary.
• bigdatacloud.com - BigDataCloud's public network lookup for 2a10:ab80:3e5::/48 attributes the prefix to ARSENIY-LIKHACHEV, shows RIPE registry assigned status, and lists AS214745 as carrier via AS207567.
• bgp.he.net - The indexed Hurricane Electric IRR page for AS213449:AS-JOW includes a RIPE-sourced AS-set remark naming Arseniy Likhacev immediately before member AS214745, last-modified 2026-05-13.
• bgp.tools - bgp.tools' personal ASN tag page lists AS214745 with Arseniy Likhacev; the direct AS214745 page was not retrievable during this search, so this is a weak attribution signal.
• hse.ru - HSE University's thesis page records a student named Arseniy Likhachev for a 2025 Software Engineering bachelor's thesis on routing research; no public source connects this page to AS214745.