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.
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.
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 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.
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.
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.
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.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
Arseniy Likhacev
Arseniy Likhacev 是一个与 AS214745 和一个 IPv6 前缀相关联的路由上下文名称，但官方注册记录认定 Vexelia Ltd 为持有者，形成了一个未解决的归属冲突，这对网络监控和事件响应具有重要意义。 另见: Letiste Praha, a. s..
为何重要
如果此人控制 AS214745，BGP 公告的变更可能会影响依赖通过 AS207567 或 AS213449 路由的网络。更直接的影响是错误归因风险：错误识别运营商可能导致错误的安全响应或资源追踪错误。 另见: 阿尔贝托·德尔加多.
公开来源显示的内容
Arseniy Likhacev 这个名字出现在与自治系统 AS214745 和 IPv6 前缀 2a10:ab80:3e5::/48 相关的公共路由数据集中。然而，AS214745 的官方注册持有者是总部位于英国的公司 Vexelia Ltd。这一未解决的冲突使得无法确认 Likhacev 是否对网络资源行使运营控制权，使得该简介成为一项关于归属风险的研究，而非确切的运营商传记。 另见: Uwe Michels.
多个公开来源在网络上下文中嵌入了该名字。BigDataCloud 的前缀查询直接将 2a10:ab80:3e5::/48 关联到 “ARSENIY-LIKHACHEV”，并将 AS214745 列为运营商。Hurricane Electric 的 IRR 记录中包含一条备注，在 AS 集合 AS213449:AS-JOW 中将 Arseniy Likhacev 与 AS214745 并列。bgp.tools 的个人 ASN 标签页面也列出了该名字，不过 AS214745 的直接页面未能获取。 另见: Chris Wood.
相比之下，Cloudflare Radar 和 IPinfo 都将 AS214745 标识为属于 Vexelia Ltd，注册于英国，网站为 vexelia.com。 另见: 尤金·贡恰连科.
这种公开记录的分歧意味着该网络的身份模糊不清。AS214745 可能是一个以公司名义注册下运营的个人项目，或者 Likhacev 这个名字可能是遗留联系人、路由遗留物或仅仅是数据录入错误。 另见: Frank Eckenfels.
没有经过验证的 RIPE 句柄、雇佣记录或公开传记能够明确将 Arseniy Likhacev 与 Vexelia Ltd 或任何其他组织的运营角色联系起来，这使得此人的实际权限存疑。 另见: 汉斯·克里斯蒂安·哈兰德.
如果 Likhacev 是实际运营商，其控制面将包括 BGP 路由发起、/48 前缀的管理，以及与上游提供商 AS207567 和相邻 AS213449 的关系。在实践中，由于控制主张未经验证，任何将 Likhacev 视为网络所有者的分析都必须与官方 RIPE 注册信息和实时路由活动进行交叉核对。 另见: 苏丹·阿尔赫利维博士.
影响机制很简单：AS214745 公告的变更可能会影响任何接受来自 AS207567 或 AS213449 路由的网络。对于监控该地区的分析师来说，更紧迫的危险是错误归因——将权限错误地分配给错误的名字可能会误导事件响应、资源追踪或威胁评估。
能够提高该简介可信度的观察点包括：对 AS214745 进行 RIPE WHOIS 直接解析，显示 Likhacev 是技术或行政联系人；由该 AS 发起的任何 BGP 公告或撤回；Vexelia Ltd 提及该个人的官方文档；或者 PeeringDB 条目将名字与活跃网络角色关联起来。
相反，如果 Vexelia Ltd 仍然是唯一的公开持有者，且在运营渠道中没有任何提及 Likhacev，那么来自路由索引网站的个人归因应被视为不可靠。
拼写变体增加了另一层谨慎。公共结果中该名字同时出现 “Likhacev” 和 “Likhachev” 两种形式，而且 HSE 大学的一篇独立学术论文提及了一位 Arseniy Likhachev，但未显示与 AS214745 的联系。在有权威来源确认此人同网络的关系之前，任何关于 Arseniy Likhacev 的简介都必须保持临时性。
运营层面
该名字出现在 IRR 备注、前缀查询和个人 ASN 标签中，暗示与路由相关的角色。然而，没有经过验证的职位、雇主或 RIPE 句柄确认其活跃运营者身份，因此该对象应被视为未解决的路由联系人归属，而非确认的网络运营商。
个人归因来源与官方 ASN 记录之间的差异造成了错误识别运营商的风险。在解决之前，将 Likhacev 视为网络所有者的分析师可能会误导监控、路由安全查核或事件处理等运营活动。
观察点
个人归因来源与官方注册数据之间的冲突使得该对象成为归因卫生的标志，而非具体的运营商简介。在该差异解决之前，赋予该名字的任何运营重要性都是推测性的，并存在误导风险。
对 AS214745 进行直接的 RIPE WHOIS 查询；该 AS 的任何 BGP 公告或撤回；Vexelia Ltd 提及 Likhacev 的官方文档；将名字与活跃角色关联的 PeeringDB 条目。
没有验证的 RIPE 句柄，没有与该网络相关的雇主或传记，拼写变体未解决，当前证据集中无活跃的 BGP 样本。
来源
- Registry RDAP / WHOIS 记录 - Arseniy Likhacev 的公开来源身份和注册上下文。
- radar.cloudflare.com - Cloudflare Radar 将 AS214745 标识为 VEXELIA-AS，别名 Vexelia，国家为英国，网站为 https://www.vexelia.com。
- ipinfo.io - IPinfo 将 AS214745 标识为位于英国的 Vexelia Ltd，注册机构 RIPE，于 2024 年 6 月 7 日分配并于 2025 年 8 月 26 日更新，其摘要中无 IPv4 或 IPv6 地址空间。
- bigdatacloud.com - BigDataCloud 针对 2a10:ab80:3e5::/48 的公共网络查询将该前缀归属为 ARSENIY-LIKHACHEV，显示 RIPE 注册状态为已分配，并将 AS214745 列为通过 AS207567 的运营商。
- bgp.he.net - 索引的 Hurricane Electric IRR 页面 AS213449:AS-JOW 包含一条源自 RIPE 的 AS 集合备注，在成员 AS214745 之前直接提及 Arseniy Likhacev，最后修改于 2026-05-13。
- bgp.tools - bgp.tools 的个人 ASN 标签页面将 AS214745 与 Arseniy Likhacev 一同列出；在此次搜索中未能获取 AS214745 的直接页面，因此这是一个弱的归因信号。
- hse.ru - HSE 大学的论文页面记录了一位名为 Arseniy Likhachev 的学生在 2025 年撰写的软件工程学士论文，主题为路由研究；无公开来源将该页面与 AS214745 关联起来。
Domain of operation
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.
- Registry RDAP / WHOIS record: Public-source identity and registry context for Arseniy Likhacev. Evidence basis: source-c1796fa2e3e6
Timeline
- Arseniy Likhacev public evidence observed
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.
Role and Scope
- Profile: Arseniy Likhacev
- Current 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.
- Analytical Category: Person
- 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.
Signal Map
- 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.
- Decision horizon: Next quarter
- Operational relevance: Medium
- Relevant activities: public operating records, official service pages, documented relationships updates
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
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.
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.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track Arseniy Likhacev?
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.
What evidence supports the profile?
Public-source identity and registry context for Arseniy Likhacev.
What should readers watch next?
The conflict between personal-attribution sources and official registry data makes this subject a marker for attribution hygiene rather than a concrete operator profile.
