Alexander Poteev is a public registry contact administratively linked to AS210871 (ARPV-RIPE). Evidence is limited to RIPE and RDAP records; no employer, biography, or operational authority is confirmed. Changes in the administrative contact or ASN registration would alter responsibility attribution. Watch for registry updates, routing visibility, or external validation of the person's role or employer.

Alexander Poteev

Alexander Poteev is the administrative contact for AS210871, listed in RIPE and RDAP records under the handle ARPV-RIPE. Only a registry-level role is confirmed; no employer, operational control, or corporate affiliation is independently verified.

Why It Matters

The impact is indirect: analysts use this registry attribution to map accountability for AS210871 and detect changes in administrative stewardship. A change in the contact or handle can indicate a re‑alignment of responsibility, though the effect relies solely on registry-record visibility and does not prove operational control.

What Public Sources Show

Alexander Poteev is the publicly listed administrative contact for Autonomous System AS210871, identified in RIPE and RDAP registry records under the handle ARPV-RIPE. The available evidence confirms only a registry-level role; no employer, operational authority, or corporate affiliation has been independently verified. This profile provides a public point of contact for accountability mapping but does not imply control over network operations or routing decisions.

Public RIPE Database searches return a person object for Alexander Poteev, linking the name to the AS210871 registration and the ARPV-RIPE identifier. A BGP.Tools page confirms that AS210871 exists in live routing-reference tooling, though it currently announces no IPv4 or IPv6 prefixes. No official biography, corporate website, or professional profile has been identified in the available evidence.

Poteev’s confirmed authority is confined to maintaining registration data for AS210871 in the RIPE Database and acting as a contact for administrative queries and abuse reports. He can update contact details and routing policy entries, but there is no public evidence that he controls prefix announcements, routing architecture, or commercial decisions tied to the autonomous system.

This contact record matters to infrastructure analysts because it provides a verifiable attribution point for AS210871, enabling accountability mapping and escalation path building. A change in the administrative contact or handle can indicate a re-alignment of ASN stewardship, making it a useful low-signal indicator when corporate context is absent.

Watchpoints include modifications to the ARPV-RIPE person object or the admin contact for AS210871, which would immediately alter the known accountability baseline. The emergence of active prefix announcements from AS210871 would elevate its infrastructure relevance. Discovery of a LinkedIn profile, corporate website, or team listing linking Poteev to a specific organization would clarify both his authority and the entity behind the ASN.

Considerable uncertainty surrounds the profile. No independent source confirms Poteev’s employer, job title, or the organization that operates AS210871. The name could be a pseudonym, and the administrative role may be held on behalf of an undisclosed entity. The entire assessment depends on the continued accuracy of public registry data.

Operating Surface

He serves as the administrative point of contact for AS210871, responsible for maintaining registration data accuracy and responding to RIPE NCC queries. This registry-defined role is limited to contact and policy record updates in the RIPE Database and does not independently confirm operational network control or commercial authority.

Alexander Poteev matters to internet infrastructure analysts because his name appears in public registry records as the contact for an autonomous system. Tracking changes to this contact can signal shifts in ASN governance or stewardship, providing a low-signal but verifiable indicator when corporate context is absent.

Watchpoints

The profile is a narrow registry-signal indicator: a real-person contact whose removal or update can flag administrative realignment for a dormant ASN. Until prefixes or corporate ties emerge, the strategic value is in accountability mapping rather than operational risk assessment.

Key watchpoints are: (1) any change to the ARPV-RIPE person object or admin contact field for AS210871; (2) announcement of IPv4/IPv6 prefixes from AS210871, which would imply active network operations; (3) public linkage of Poteev to a known organization via corporate registries, LinkedIn, or team pages.

Missing data includes Poteev’s legal employer, his authority scope within any parent organization, the presence of PeeringDB or official website records, and any public attribution to a registered company. Filling these gaps would convert the profile from registry-contact to operator-level intelligence.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for Alexander Poteev.
• RIPE registry record - RIPE Database web search returns a person object for Alexander Poteev, supporting that the name appears in public RIPE registration data.
• RIPE registry record - RIPE Database web search for ARPV-RIPE supports that the ARPV-RIPE handle is a public registry identifier connected to Alexander Poteev.
• bgp.tools - BGP.Tools provides a public routing-context page for AS210871, useful as supporting context that the ASN exists in live routing-reference tooling.