Anton V. Bogachenkov
Anton V. Bogachenkov appears in RIPE registry data as the administrative and technical contact for AS210989 (handle AVB499-RIPE), serving as the sole public human link to that autonomous system with no verified employer or operational authority beyond contact registration.
Why It Matters
Changes to his registry record could indicate a transition of operational control for AS210989, potentially affecting routing security assumptions. His removal would break the only public contact chain, complicating incident response and raising the risk profile of the autonomous system. Continuity supports the stability of any downstream dependency analysis that relies on the current registration.
What Public Sources Show
Anton V. Bogachenkov is listed in RIPE registry data as the administrative and technical contact for autonomous system AS210989 under handle AVB499-RIPE. He is the sole named human link to that ASN in public records, providing a starting point for mapping operational governance.
The role is a contact registration, not an indication of authority. RIPE policy states that person entities exist for contact purposes and do not confer control over number resources. No evidence independently verifies Bogachenkov’s employer, technical authority, or any operational control.
Infrastructure analysts use registry contacts to build dependency maps and prepare incident response. Persistence of Bogachenkov’s record suggests administrative stability for AS210989. A sudden change or removal could signal a handover, abandonment, or increase the risk of hijacking.
Three public sources support this profile. The RDAP record for AS210989 confirms the contact role. A RIPE WHOIS query for AVB499-RIPE shows the person entity. RIPE database documentation clarifies that such entities are for contacts, not authority, and that the maintainer entity holds actual control.
The public control surface is limited to receiving inquiries directed to the admin/tech contact. Bogachenkov has no documented ability to modify AS210989’s registration or routing. Actual authority rests with the maintainer entity, which has not been examined in this evidence set.
Key watchpoints include changes to the registry record, the appearance or withdrawal of BGP prefixes for AS210989, and the expansion of the AVB499-RIPE handle to other resources. Any of these would alter the assessed significance and risk associated with this contact.
Considerable uncertainty clouds the profile. The real-world identity behind the handle is unconfirmed; the record may be outdated or maintained by a third party. RIPE NCC auditing can invalidate stale person entities, breaking the public contact chain. Analysts should treat this as a registry anchor, not a verified authority.
Operating Surface
He serves as the registrant contact for AS210989, meaning his contact details are published in the RIPE database for administrative and technical queries. The role is limited to contact registration; there is no evidence of employer affiliation, operational control over the ASN's routing, or ownership of the resources.
Infrastructure analysts rely on registry contacts to map the human governance layer of internet number resources. By appearing as the sole named contact for AS210989, Bogachenkov provides a public anchor point for operational inquiries, incident response, and continuity tracking. His persistence suggests stability; a sudden change or removal could indicate transition of control, abandonment, or risk of hijacking.
Watchpoints
Bogachenkov serves as a stability indicator for AS210989. His continued presence suggests the ASN remains under consistent administration; his removal would break the only public contact, increasing operational risk. The lack of routing activity makes the ASN itself a low-visibility asset, but its contact anchor is a point of leverage for incident responders.
Monitor the RIPE registry for any changes to AVB499-RIPE’s association with AS210989. Track BGP routing tables for any prefix announcements by AS210989. Watch for the same handle appearing on other ASNs or inetnums. RIPE NCC audits may invalidate the handle, triggering a contact vacuum.
The maintainer entity for AS210989 has not been analyzed, leaving the true controlling entity unknown. No employer, biography, or professional profile exists for Bogachenkov, so his operational competence and current involvement are unassessed. BGP and prefix data are absent, limiting assessment of the ASN’s active footprint.
Sources
- Registry RDAP / WHOIS record - public-source identity and registry context for Anton V. Bogachenkov.
- Registry RDAP / WHOIS record - RIPE's public WHOIS web interface is the authoritative public registry surface where the entity handle AVB499-RIPE can be checked for existence and associated registration details.
- RIPE registry record - RIPE documents public database entity types used for contact and registration data, providing context for interpreting named person or role contacts in RIPE registry records.
