Registry contacts are tracked because they represent a publicly visible authority surface for Internet number resources. A change in the listed contact for AS211916 could signal an organizational restructuring, merger, or unauthorized modification, affecting downstream networks that depend on the AS.
AuteurClaire Shen
Editorial owner accountable for this profile route.
Temps de lecture3 min
Estimated reading time at standard editorial pace.
Publié leMay 26, 2026
Date this profile last entered editorial circulation.
Last updateJun 03, 2026
Date this profile last entered editorial circulation.
CategoryIndividual registry-holder label
Controlled classification used for cross-profile comparison.
RégionEurope
Primary geography where current signals are most visible.
Signal FocusInstitution Type
Principal area tracked in this intelligence profile.
Type de contenuProfile
Structured profile used for cross-category comparison.
Domaine principalInfrastructure
Primary editorial domain framing the analysis.
SujetRegistry contact intelligence
Controlled taxonomy label used for this profile route.
HorizonQUARTER_30_120D
Most likely window for strategy or governance effects.
ImpactMediumThe signal alters planning assumptions but usually requires secondary implementation before full effect.
Confiance0.95
Anchored to multiple primary-source references and direct disclosures.
Dossier de preuves
Sources primaires utilisées pour la classification et l'évaluation d'impact.
Liviu Poenaru is the admin and tech contact for AS211916 per the RIPE NCC RDAP record, offering a narrow but authoritative signal of administrative control over the autonomous system. No employer, organization, routing footprint, or corroborating source is available, so the profile is bounded by the registry entry. The primary watchpoint is any change to the LP12365-RIPE handle, which would trigger a reassessment of resource control. The main gap is the absence of independent identity confirmation and real-world operational context.
Core Entity Brief
Core Entity Brief
Entity
Liviu Poenaru
Public role
Registry contacts are tracked because they represent a publicly visible authority surface for Internet number resources. A change in the listed contact for AS211916 could signal an organizational restructuring, merger, or unauthorized modification, affecting downstream networks that depend on the AS.
Region
Europe
Category
Individual registry-holder label
Primary domain
Infrastructure
Signal focus
Institution Type
Time horizon
QUARTER_30_120D
Impact
Medium
Confidence
0.95
Evidence coverage
1 public source reference
Related coverage
Profile anchor article
Website
Public evidence pending
Last update
Jun 03, 2026
Liviu Poenaru is an individual without an identified corporate entity; the supplied evidence reflects only a personal registry contact role for AS211916.
What It Does
Contact authority: The subject's role is not commercial; it enables administrative management of AS211916 under RIPE rules without generating revenue or representing a company.
Registry stewardship: The function involves stewarding the ASN registration, including updating technical and administrative details to maintain accurate routing information in the public record.
Operating Snapshot
Registry presence: The subject appears solely through the RIPE NCC RDAP record with handle LP12365-RIPE, holding admin and tech roles for AS211916.
Routing activity: No BGP announcements, PeeringDB network entry, or operational prefix data are associated with Liviu Poenaru; the person's involvement in routing operations is unconfirmed.
Control Surface
Registry database: The primary control surface is the RIPE NCC registry entry for AS211916, through which the LP12365-RIPE handle can initiate updates to the autonomous system's record.
Abuse handling: As technical contact, the subject is the designated recipient for abuse reports related to the AS, though actual responsiveness depends on internal processes not visible publicly.
Watchpoints
Contact changes: Any modification to the LP12365-RIPE handle or its association with AS211916 could signal an administrative or ownership change needing investigation.
New public data: The appearance of a LinkedIn profile, company website, or PeeringDB entry linking Liviu Poenaru to a specific employer would enhance the understanding of operational context and authority.
Domain of operation
Registry contacts are tracked because they represent a publicly visible authority surface for Internet number resources. A change in the listed contact for AS211916 could signal an organizational restructuring, merger, or unauthorized modification, affecting downstream networks that depend on the AS.
Public role: Liviu Poenaru is framed by registry contacts are tracked because they represent a publicly visible authority surface for internet number resources. a change in the listed contact for as211916 could signal an organizational restructuring, merger, or unauthorized modification, affecting downstream networks that depend on the as. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record
Operating surface: Registry contact intelligence and Europe provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record
Timeline
Liviu Poenaru public profile updated
Public coverage records Liviu Poenaru as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: Registry contacts are tracked because they represent a publicly visible authority surface for Internet number resources. A change in the listed contact for AS211916 could signal an organizational restructuring, merger, or unauthorized modification, affecting downstream networks that depend on the AS.
Object role: Liviu Poenaru holds both the admin-c and tech-c roles for AS211916 according to the RIPE NCC RDAP database. This positions the individual as a formal point of contact for administrative updates, technical management, and potential resource transfers, though the extent of actual decision-making authority beyond the registry is unconfirmed.
Impact note: If the contact details for LP12365-RIPE are altered without accompanying public explanation, network operators, security analysts, and peers of AS211916 may need to reassess the trustworthiness and stability of routes originating from that autonomous system, potentially impacting traffic engineering and security posture.
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 Liviu Poenaru 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 Liviu Poenaru included?
Liviu Poenaru 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.
