Bashinskii Vadim Ruslanovich is a person known only through RIPE registry records, where the name controls a small AS and prefix. The thesis is that the subject's importance is purely as a registry attribution point, and the key risk is the concentration of control in a single name with no external verification. Evidence is consistent but narrow, and future developments to the registry objects or network footprint are the main watchpoints. Uncertainty about the individual's real identity, the business behind net-host, and the split geographic signals should prevent analysts from overreading commercial or biographical claims.

Bashinskii Vadim Ruslanovich

Bashinskii Vadim Ruslanovich is the public name attached to RIPE organisation ORG-BVR4-RIPE, maintainer BASHIN-MNT, and autonomous system AS216473 (net-host). The individual's role is limited to registry and routing records: no independent biography, corporate website, or service description exists outside those sources.

For infrastructure analysts, the subject matters as a single point of attribution for a small but live network footprint, and any change to the underlying registry objects would shift operational responsibility.

Why It Matters

Changes to the registry holder or contact records, maintainer references, upstream policy, route origin, RPKI state, or prefix announcements would alter how operators identify the responsible party for the net-host footprint and how they reach its resources. The network’s small scale—a single /24—means even minor reconfigurations can disrupt reachability for hosted services, while the absence of alternative contacts concentrates operational risk in one named individual.

What Public Sources Show

Bashinskii Vadim Ruslanovich is the name that appears across RIPE registry records as the organisational contact and holder for autonomous system AS216473 and its associated resources. No independent biography, corporate website, or professional profile exists outside those records, so understanding this subject means examining the public infrastructure tied to that name and the operational risk it concentrates.

The registry evidence is consistent across multiple sources. RIPE WHOIS and RDAP data show the individual attached to organisation handle ORG-BVR4-RIPE, maintainer BASHIN-MNT, and role object BV3757-RIPE. The autonomous system, listed with the as-name net-host, was created on 10 July 2025 and last modified two days later.

Third-party intelligence platforms—BGP.tools, IPLocate, IPinfo, BigDataCloud—all confirm the linkage and add that the network announces a single IPv4 prefix, 80.66.83.0/24, which carries a valid RPKI status. The only observed upstream is AS51765, operated by Oy Crea Nova Hosting Solution Ltd, and no downstreams are reported.

The control surface is limited to what the registry objects permit. The name on ORG-BVR4-RIPE and BASHIN-MNT gives the subject authority to modify RIPE resource records, manage routing policy for the prefix, and handle abuse reports. Because the footprint is small—256 addresses and no IPv6—any change to those records shifts responsibility immediately.

If the maintainer is replaced or the contact abandoned, the network’s operational accountability becomes uncertain for anyone relying on its reachability.

A geographic split adds a layer of complexity. The AS and organisation registration point to Kazakhstan, yet the inetnum object for the 80.66.83.0/24 prefix carries a Finnish country code. This discrepancy appears in multiple data sets and has not been publicly explained. Operators and compliance officers who rely on registry country fields for jurisdictional decisions should treat the network’s situs as ambiguous until further evidence emerges.

The impact of this subject hinges on attribution and operational reachability. Because the registry records name a single individual as the responsible party, the loss or replacement of that name would create a void that could delay abuse mitigation or complicate routing policy updates.

Meanwhile, the network’s RPKI-valid state and visible upstream dependency mean it is a live part of the routing system, even if its service type remains uncertain—third-party classifiers disagree on whether it is hosting, ISP, or content.

Readers should watch four signals. First, any change to the ORG-BVR4-RIPE, BASHIN-MNT, or BV3757-RIPE records would alter the public baseline for attribution. Second, new prefix announcements, IPv6 adoption, or a change in upstream would expand the operational significance of the subject. Third, the emergence of independent public information—a corporate registration, a personal website, or a media mention—would strengthen or challenge the current picture.

Fourth, resolution of the Kazakhstan/Finland geographic split would clarify the network’s jurisdictional exposure.

The evidence for this profile comes from official registry queries and independent AS-intelligence services. RIPE RDAP and WHOIS sources provide the core identity linkage, while BGP.tools, IPLocate, IPinfo, and BigDataCloud replicate and supplement the routing context. All sources are low-risk, publicly accessible, and collectively establish that Bashinskii Vadim Ruslanovich is the controlling name for a small but active Internet number resource portfolio.

Operating Surface

The subject serves as the named administrative and technical contact for a small set of Internet number resources under the RIPE NCC. Through organisation handle ORG-BVR4-RIPE and role object BV3757-RIPE, the name appears on the maintainer BASHIN-MNT, the AS216473 aut-num, and the 80.66.83.0/24 inetnum and route objects. The role grants authority to modify resource records, manage routing policy, and receive abuse reports for the net-host footprint.

The subject is tracked because the continuity of the registry records directly determines who operators and regulators treat as accountable for the network. If the name disappears from ORG-BVR4-RIPE or BASHIN-MNT, or if the AS footprint changes, the attribution and risk profile of the small net-host network shift immediately. Public routing data shows the network is active and RPKI-valid, making it a live dependency for upstream and downstream parties.

Watchpoints

The subject is a registry-fingerprint identity with no commercial or personal depth. Strategically, the value lies in monitoring this single point of control: if the name persists, the network’s accountability is stable; if the name is replaced or the footprint changes, it signals a potential transfer of control or re-purposing of the resources.

The split geographic signals add a compliance nuance that could become material in sanctions or jurisdiction-based routing scenarios.

1. Registry record changes (ORG-BVR4-RIPE, BASHIN-MNT, BV3757-RIPE). 2) New prefix announcements or upstream/downstream changes. 3) Appearance of independent public identification (e.g., corporate registration, personal website, media). 4) Clarification of the FI/KZ geographic discrepancy. 5) Any RPKI invalidation or route-object modification.

The most significant gap is the absence of any personal or corporate biography, employment record, or legal registration for the underlying entity. Additional public-web collection targeting Kazakhstan or Finland business registries, net-host.org content, and social/professional networks could fill the gap. Also missing: any service description, customer references, or PeeringDB entry that would confirm the network’s business model.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for Bashinskii Vadim Ruslanovich.
• bgp.tools - BGP.tools lists AS216473 as Bashinskii Vadim Ruslanovich, registered to ORG-BVR4-RIPE, active under RIPE, with one IPv4 prefix, upstream AS51765, and RIPE WHOIS lines for org-name, maintainer, creation, and modification dates.
• iplocate.io - IPLocate lists AS216473 as Bashinskii Vadim Ruslanovich, AS name NET-HOST, country Kazakhstan, website net-host.org, 256 IPv4 addresses, no IPv6, allocated July 10, 2025, and one upstream AS51765.
• ipinfo.io - IPinfo lists AS216473 as Bashinskii Vadim Ruslanovich with net-host.org, Kazakhstan, 256 IPv4 addresses, no IPv6, Hosting type, one peer/upstream AS51765, no downstreams, and two hosted domains redacted in the public view.
• Registry RDAP / WHOIS record - 2ip.io reproduces RIPE WHOIS showing AS216473, as-name net-host, org ORG-BVR4-RIPE, admin/tech contact role BV3757-RIPE, maintainer BASHIN-MNT, and org-name Bashinskii Vadim Ruslanovich.
• Registry RDAP / WHOIS record - Whois.com reproduces RIPE inetnum and route data for 80.66.83.0 to 80.66.83.255, showing netname Bashinskii, org ORG-BVR4-RIPE, country FI for the inetnum, maintainer BASHIN-MNT, and route origin AS216473.
• bigdatacloud.com - BigDataCloud lists AS216473 organisation as Bashinskii Vadim Ruslanovich, name net-host, registry RIPE, registered country Kazakhstan, 256 IPv4 addresses, one IPv4 prefix, no IPv6 prefixes, and receiving from AS51765.
• ipinfo.io - IPinfo's prefix page lists 80.66.83.0/24 as belonging to AS216473 and Bashinskii Vadim Ruslanovich, registered with RIPE, with RPKI valid status in the public summary.