Kazakov Aleksandr is the sole named holder of AS210778 (NTKOM-AS), a small Russian network originating the 93.170.112.0/23 prefix and relying on transit from TransTeleCom and ER-Telecom. All public evidence is registry-derived; no corporate or biographical sources exist. Operational control is concentrated in a single maintainer handle (NTKOM-MNT), making the subject a single point of failure for routing continuity. The profile serves as a monitoring baseline registry changes, BGP anomalies, and any expansion of the public footprint that would alter the operating-concentration thesis.
Kazakov Aleksandr appears in RIPE registry records as the administrative and technical contact for autonomous system AS210778. The public evidence describes a resource-holder role, not a verified biographical profile.
The subject holds sole maintainer access (NTKOM-MNT) to the AS and associated prefix, concentrating operational control. Changes to registry data or BGP announcements directly affect reachability of the 93.170.112.0/23 address block.
The subject holds sole maintainer access (NTKOM-MNT) to the AS and associated prefix, concentrating operational control. Changes to registry data or BGP announcements directly affect reachability of the 93.170.112.0/23 address block.
Kazakov Aleksandr appears in RIPE registry records as the administrative and technical contact for autonomous system AS210778. The public evidence describes a resource-holder role, not a verified biographical profile.
Any registry update, route object modification, or upstream change can propagate routing instability or lost connectivity for the 512 IPv4 addresses announced by AS210778. Monitoring the subject helps analysts anticipate network-operations disruptions.
Kazakov Aleksandr is the sole named holder of AS210778 (NTKOM-AS), a small Russian network originating the 93.170.112.0/23 prefix and relying on transit from TransTeleCom and ER-Telecom. All public evidence is registry-derived; no corporate or biographical sources exist. Operational control is concentrated in a single maintainer handle (NTKOM-MNT), making the subject a single point of failure for routing continuity. The profile serves as a monitoring baseline registry changes, BGP anomalies, and any expansion of the public footprint that would alter the operating-concentration thesis.
Any registry update, route object modification, or upstream change can propagate routing instability or lost connectivity for the 512 IPv4 addresses announced by AS210778. Monitoring the subject helps analysts anticipate network-operations disruptions.
| 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
卡扎科夫·亚历山大
卡扎科夫·亚历山大是AS210778（NTKOM-AS）的唯一公开上市个体，这是一个小型俄罗斯IPv4网络，通过TransTeleCom和ER-Telecom进行上游传输。所有证据均来自注册数据；没有经过验证的传记或公司网站。 另见: Security team.
为什么重要
任何注册更新、路由对象修改或上游变更都可能导致AS210778宣布的512个IPv4地址的路由不稳定或连接中断。监控该主体有助于分析师提前预测网络运营中断。 另见: Dcent Investments BV.
公开来源显示什么
卡扎科夫·亚历山大是自治系统AS210778（NTKOM-AS）的唯一命名持有者和行政联系人，这是一个完全依赖两家较大运营商传输的小型俄罗斯网络。关于此人的所有公开信息均来自RIPE注册和路由记录；不存在经过验证的传记、雇主或个人网站。 另见: FGSZ Zrt..
这种集中控制使该主体对任何跟踪IPv4前缀93.170.112.0/23及其运营依赖性的分析师都很重要。 另见: gegatelecom.
网络规模适中：AS210778于2021年9月分配，宣布覆盖512个地址的/23前缀，以及更具体的/24。根据公共IP数据库，该AS注册在俄罗斯联邦，并定位在布良斯克州纳夫利亚。上游连接通过AS20485（TransTeleCom股份公司）和AS9049（ER-Telecom控股股份公司）进行。 另见: hr-backoffice Ured za podrsku d.o.o..
未发现任何IPv6地址的宣布，也未找到公共PeeringDB条目或公司网站。 另见: sift-ltd.
多个独立平台——RIPEstat、IPinfo、IPIP、IPGeolocation、Cloudflare Radar和IPAddress.com——都显示相同的名称“卡扎科夫·亚历山大”作为AS持有者。RIPE WHOIS数据标识组织ORG-KA918-RIPE，赞助组织为ORG-ATS13-RIPE。维护者对象NTKOM-MNT是主体更新注册条目和路由策略的技术途径。这些来源一致，但均未提供注册层之外的个人或企业验证。 另见: Uwe Michels.
由于AS210778的控制权掌握在单一维护者手中，任何注册修改或路由对象更改都可能立即影响93.170.112.0/23前缀。配置错误、意外撤销或注册过期可能会中断依赖该地址块的任何服务。由于该网络完全依赖两家上游运营商，对等互联安排的变更也将迅速传播到全球路由表。 另见: 尤金·贡恰连科.
监控该主体可以为俄罗斯互联网这一角落的行政或运营动荡提供早期预警信号。
分析师应监控AS210778的aut-num对象、路由对象和RIPE组织记录是否有任何修改。PeeringDB条目、公司网站或外部雇主信息的增加将扩展有限的证据基础，并可能改变对运营集中度的评估。
出现来自该AS的IPv6声明将表明技术升级。前缀突然重新分配到不同的ASN，或赞助组织发生变化，将从根本上改变控制面，需要重新评估该主体的相关性。
“卡扎科夫·亚历山大”这个名字可能代表个人或角色账户；没有独立的个人身份得到证实。注册联系数据可能已过时，主体的权限可能不超出RIPE行政操作。不同来源之间存在地址数量差异，因为一些来源聚合了重叠的前缀，但观察到的BGP公告仍然是明确的信号。
没有直接的公开声明或传记，该资料应被视为注册和路由监控的基线，而不是全面的个人画像。
运营面
卡扎科夫·亚历山大出现在RIPE注册记录中，作为自治系统AS210778的行政和技术联系人。公开证据描述的是资源持有者角色，而不是经过验证的传记资料。
该主体拥有对AS和相关前缀的唯一维护者访问权限（NTKOM-MNT），集中了运营控制。注册数据或BGP公告的变化直接影响93.170.112.0/23地址块的可达性。
观察点
运营控制集中在单个人身上增加了配置错误和连续性缺口的风险。这使得AS210778成为监测依赖两个上游运营商的小型俄罗斯网络运营健康状况的有效示警器。
对aut-num或路由对象进行注册更改、新前缀公告或赞助组织变化都将改变该资料。PeeringDB或网站存在的发现将扩展证据。
不存在传记或雇主数据；主体目前的权力未经证实；联系方式可能过时；不清楚任何客户或服务合同。
来源
- 互联网注册记录 - RIPEstat AS210778概述根据RIPE WHOIS提供持有者名称和公告上下文。
- RIPE注册记录 - 文档确认AS概述端点返回ASN状态和WHOIS中的持有者名称。
- ipinfo.io - IPinfo将AS210778列为卡扎科夫·亚历山大，俄罗斯，前缀93.170.112.0/23、/24，上游AS20485和AS9049。
- 注册RDAP / WHOIS记录 - IPinfo前缀详情显示RIPE WHOIS中93.170.112.0 - 93.170.113.255，网络名NTKOM-NET，组织ORG-KA918-RIPE。
- 注册RDAP / WHOIS记录 - IPIP将AS210778列为NTKOM-AS - 卡扎科夫·亚历山大，注册机构RIPE，组织ORG-KA918-RIPE，赞助组织ORG-ATS13-RIPE，上游策略与AS9049和AS20485。
- ipgeolocation.io - IPGeolocation将AS210778列为卡扎科夫·亚历山大，分配于2021-09-10，三条IPv4路由，上游AS9049和AS20485。
- radar.cloudflare.com - Cloudflare Radar将AS210778标识为俄罗斯联邦的NTKOM-AS，提供BGP公告和异常监测。
- ipaddress.com - 描述93.170.112.0/23为由AS210778公告的512个地址IPv4子网，位于俄罗斯布良斯克州纳夫利亚。
Domain of operation
Kazakov Aleksandr is the sole publicly listed individual for AS210778 (NTKOM-AS), a small Russian IPv4 network with upstream transit from TransTeleCom and ER-Telecom. All evidence is registry-derived; no verified biography or corporate website exists.
- Internet registry record: RIPEstat AS overview for AS210778 provides holder name and announcement context according to RIPE WHOIS. Evidence basis: source-e79a22617157
Timeline
- Kazakov Aleksandr public evidence observed
The subject holds sole maintainer access (NTKOM-MNT) to the AS and associated prefix, concentrating operational control. Changes to registry data or BGP announcements directly affect reachability of the 93.170.112.0/23 address block.
At A Glance
- Name: Kazakov Aleksandr
- Type: Individual registry-holder label
- Base: Russia
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- documented relationships updates
Why It Matters
- Any registry update, route object modification, or upstream change can propagate routing instability or lost connectivity for the 512 IPv4 addresses announced by AS210778. Monitoring the subject helps analysts anticipate network-operations disruptions.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
Any registry update, route object modification, or upstream change can propagate routing instability or lost connectivity for the 512 IPv4 addresses announced by AS210778. Monitoring the subject helps analysts anticipate network-operations disruptions.
Longer-term relevance depends on verified operating, policy, and relationship changes.
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
Any registry update, route object modification, or upstream change can propagate routing instability or lost connectivity for the 512 IPv4 addresses announced by AS210778. Monitoring the subject helps analysts anticipate network-operations disruptions.
Watchpoints
- The concentration of operational control in a single person increases the risk of configuration errors and continuity gaps.
- That makes AS210778 a useful canary for operational hygiene in small Russian networks that rely on two upstreams.
- Registry changes to the aut-num or route objects, new prefix announcements, or changes in the sponsoring organisation would alter the profile.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track Kazakov Aleksandr?
The subject holds sole maintainer access (NTKOM-MNT) to the AS and associated prefix, concentrating operational control. Changes to registry data or BGP announcements directly affect reachability of the 93.170.112.0/23 address block.
What evidence supports the profile?
RIPEstat AS overview for AS210778 provides holder name and announcement context according to RIPE WHOIS.
What should readers watch next?
The concentration of operational control in a single person increases the risk of configuration errors and continuity gaps.
