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.
AuthorJocelyn Fang
Editorial owner accountable for this profile route.
Reading Time3 min
Estimated reading time at standard editorial pace.
PublishedMay 26, 2026
Date this profile last entered editorial circulation.
Last updateJun 02, 2026
Date this profile last entered editorial circulation.
CategoryIndividual registry-holder label
Controlled classification used for cross-profile comparison.
RegionGlobal
Primary geography where current signals are most visible.
Signal FocusInstitution Type
Principal area tracked in this intelligence profile.
Content TypeProfile
Structured profile used for cross-category comparison.
Primary DomainInfrastructure
Primary editorial domain framing the analysis.
TopicInfrastructure registry contact
Controlled taxonomy label used for this profile route.
Time HorizonQuarter (30-120d)
Most likely window for material strategy effects.
ImpactMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
Confidence0.95
Anchored to multiple primary-source references and direct disclosures.
Evidence Pack
Primary-source references used for classification and impact scoring.
Anton V. Bogachenkov is the admin/tech contact for AS210989 in RIPE registry (handle AVB499-RIPE). This profile draws on three public sources: the ASN’s RDAP record, a RIPE WHOIS query, and RIPE database documentation. No employer, biography, or routing context exists. He provides a contact anchor, but real authority sits with the unexamined maintainer. Watchpoints: contact removal, handle expansion, registry audit. High uncertainty about real identity and current relevance.
Core Entity Brief
Core Entity Brief
Entity
Anton V. Bogachenkov
Public role
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.
Region
Global
Category
Individual registry-holder label
Primary domain
Infrastructure
Signal focus
Institution Type
Time horizon
Quarter (30-120d)
Impact
Medium
Confidence
0.95
Evidence coverage
3 public source references
Related coverage
Profile anchor article
Website
Public evidence pending
Last update
Jun 02, 2026
Anton V. Bogachenkov is a registry contact for AS210989 in the RIPE database.
What It Does
Registry contact service: The listed roles are administrative and technical contact for the autonomous system AS210989. The entity receives any queries directed to those contact points, but has no documented commercial or operational activity beyond registration.
Commercial absence: No evidence of revenue generation, customer contracts, or commercial services has been found. The registration does not imply active business operations.
Operating Snapshot
Registry presence: Anton V. Bogachenkov is recorded with handle AVB499-RIPE as a person object in the RIPE database, associated with AS210989 as admin and tech contact.
Active routing: No BGP announcements or assigned prefixes for AS210989 are observed in the current evidence set, so the operating footprint is limited to the registry entry.
Control Surface
Contact registration: The entity controls the receipt of communications directed to the admin/tech roles. Actual authority to modify the ASN's registration depends on the maintainer object (mnt-by), which is unexamined.
Evidence sensitivity: New registry or routing evidence could change the assessed operational significance of this contact.
Watchpoints
Registry changes: Alterations to the ASN's RDAP or WHOIS record would signal possible administrative shifts.
Role expansion: Appearance of the same handle on additional ASNs or IP resources would indicate a broader operational role and warrant investigation.
Domain of operation
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.
Public role: Anton V. Bogachenkov is framed by 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. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record; Registry RDAP / WHOIS record
Operating surface: Infrastructure registry contact and Global provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record; Registry RDAP / WHOIS record
Timeline
Anton V. Bogachenkov public profile updated
Public coverage records Anton V. Bogachenkov as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: 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.
Object role: 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.
Impact note: 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.
Control surface: public operating records, official service pages, source-backed relationship updates
Key dependencies: official company sources, public registries, operator-published records
Public View
The public read of Anton V. Bogachenkov is limited to visible role, operating context, and relationship evidence.
Watchpoints
New public role, affiliation, product, policy, or market disclosures.
Verified relationship changes involving named organizations or people.
Caveats
Private or unverified claims are excluded from this public view.
FAQ
Why is Anton V. Bogachenkov included?
Anton V. Bogachenkov has public evidence that makes the institution relevant to BTW's coverage of digital infrastructure, governance, or markets.
What is public about this profile?
The public layer covers visible role, operating context, linked organizations, and evidence-backed watchpoints.
What should readers watch next?
Readers should watch for source-backed role changes, new partnerships, regulatory exposure, operating expansion, or evidence that changes the public assessment.
