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

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.

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.

What Public Sources Show

Kazakov Aleksandr is the sole named holder and administrative contact for autonomous system AS210778 (NTKOM-AS), a small Russian network that depends entirely on transit from two larger carriers. All public knowledge about this individual comes from RIPE registry and routing records; no verified biography, employer, or personal website exists.

This concentrated control makes the subject material for any analyst tracking the continuity of the IPv4 prefix 93.170.112.0/23 and its operational dependencies.

The network footprint is modest: AS210778 was allocated in September 2021 and announces the /23 prefix covering 512 addresses, with more-specific /24s. The AS is registered in the Russian Federation and geolocates to Navlya, Bryansk Oblast, according to public IP databases. Upstream connectivity flows through AS20485 (Joint Stock Company TransTeleCom) and AS9049 (JSC ER-Telecom Holding).

No IPv6 addresses are announced, and no public PeeringDB entry or company website has been discovered.

Multiple independent platforms—RIPEstat, IPinfo, IPIP, IPGeolocation, Cloudflare Radar, and IPAddress.com—all surface the same name “Kazakov Aleksandr” as the AS holder. The RIPE WHOIS data identifies organisation ORG-KA918-RIPE with sponsoring organisation ORG-ATS13-RIPE. The maintainer object NTKOM-MNT is the technical handle through which the subject can update registry entries and routing policy. These sources are consistent, but none provide personal or corporate verification beyond the registry layer.

Because the control of AS210778 rests with a single maintainer handle, any registry modification or route object change can instantly affect the 93.170.112.0/23 prefix. A misconfiguration, unexpected withdrawal, or expired registration could interrupt connectivity for whatever services depend on that address block. Since the network relies exclusively on two upstream carriers, alterations in those peering arrangements would also propagate quickly through global routing tables.

Monitoring the subject offers an early-warning signal for administrative or operational turbulence in this corner of the Russian internet.

Analysts should monitor the AS210778 aut-num object, route objects, and RIPE organisation records for any modification. The addition of a PeeringDB entry, a corporate website, or an external employer affiliation would expand the limited evidence base and could alter the assessment of operational concentration.

The appearance of IPv6 announcements from the AS would indicate a technical upgrade. A sudden reassignment of the prefix to a different ASN, or a change in the sponsoring organisation, would fundamentally shift the control surface and require reassessment of the subject’s relevance.

The name “Kazakov Aleksandr” may represent an individual or a role account; no independent personal identification has been corroborated. Registry contact data could be outdated, and the subject’s authority may not extend beyond RIPE administrative operations. Address count discrepancies exist across sources because some aggregate overlapping prefixes, but the observed BGP announcements remain the definitive signal.

Without a direct public statement or biography, the profile should be treated as a baseline for registry and routing vigilance, not as a comprehensive personal portrait.

Operating Surface

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.

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. Discovery of PeeringDB or website presence would expand evidence.

No biographical or employer data exists; the subject's current authority is unverified; contact details may be stale; no customer or service contracts are known.

Sources

• Internet registry record - RIPEstat AS overview for AS210778 provides holder name and announcement context according to RIPE WHOIS.
• RIPE registry record - Documentation confirms the AS overview endpoint returns ASN status and holder name from WHOIS.
• ipinfo.io - IPinfo lists AS210778 as Kazakov Aleksandr, Russia, with prefixes 93.170.112.0/23, /24, and upstreams AS20485 and AS9049.
• Registry RDAP / WHOIS record - IPinfo prefix details show RIPE WHOIS for 93.170.112.0 - 93.170.113.255, netname NTKOM-NET, org ORG-KA918-RIPE.
• Registry RDAP / WHOIS record - IPIP lists AS210778 as NTKOM-AS - Kazakov Aleksandr, registry RIPE, org ORG-KA918-RIPE, sponsoring-org ORG-ATS13-RIPE, upstream policy with AS9049 and AS20485.
• ipgeolocation.io - IPGeolocation lists AS210778 as Kazakov Aleksandr, allocated 2021-09-10, three IPv4 routes, upstreams AS9049 and AS20485.
• radar.cloudflare.com - Cloudflare Radar identifies AS210778 as NTKOM-AS in Russian Federation, with BGP announcement and anomaly monitoring.
• ipaddress.com - Describes 93.170.112.0/23 as a 512-address IPv4 subnet advertised by AS210778, geolocated to Navlya, Bryansk Oblast, Russia.