Ioannis Karamperis is a thin intelligence profile built from a single RIPE RDAP contact record for AS210365. The only verified fact is that a person with this name holds the admin and tech roles for an autonomous system assigned to Fragnet AB, a Swedish game-server host. No independent biography, employer confirmation, or routing activity has been observed. The profile serves as a monitoring baseline registry record changes and future routing events; it requires caution because the contact listing could be stale, symbolic, or unassociated with the actual network operator. Watchpoints include contact turnover, prefix announcements, and any additional industry presence.

Ioannis Karamperis

Ioannis Karamperis is a publicly listed RIPE RDAP administrative and technical contact for AS210365, an autonomous system operated by Fragnet AB, a Swedish game server hosting provider. The profile is built solely on registry and company web evidence, with no independent biographical verification.

He serves as a visible attribution point for the ASN, and changes to his record or routing activity from AS210365 are the primary watchpoints for analysts tracking this infrastructure.

Why It Matters

A change in the RDAP or WHOIS record for AS210365 would immediately alter the attribution picture for anyone relying on Fragnet’s infrastructure. The sudden appearance of BGP announcements from the ASN would increase operational visibility. Currently, his impact is limited to registry coordination and abuse contact response, but that can change quickly with new evidence.

What Public Sources Show

Ioannis Karamperis is listed in RIPE RDAP records as the administrative and technical contact for autonomous system AS210365. The ASN is registered to FRAGNET and operated by the Swedish hosting company Fragnet AB, which specializes in game server infrastructure. No independent biography or employer confirmation exists for him outside this registry entry.

Registry contacts serve as operational tripwires: they give network operators, abuse desks, and researchers a named party responsible for an ASN. A person attached to an ASN record enables attribution for routing incidents and shifts in hosting infrastructure. Tracking changes to this contact entry can therefore signal administrative turnover or network reassignment.

The public evidence is limited to four official sources: the RIPE RDAP lookup for AS210365, a RIPEstat overview confirming the ASN name, an OpenCorporates listing for Fragnet AB, and the company’s own website. These collectively place Karamperis in the admin/tech role for the ASN used by Fragnet. They do not, however, provide a job title, employment history, or any personal details.

His operating surface is purely informational. The RDAP entry is the only verified mechanism through which the public can associate him with AS210365. There is no evidence that he controls routing policy, network hardware, or company finances. His role is limited to registry maintenance and abuse handling coordination.

Watchpoints include any modification of the RDAP or WHOIS record for AS210365, the emergence of BGP announcements from the ASN, and new appearances in PeeringDB or other RIPE handles. A change in contact details would alter the baseline for attribution. Active routing announcements would increase his operational visibility.

Uncertainty is high. The name appears only once in a registry record, with no supporting corporate biography, professional network profile, or public affiliation. The listing could be stale, outsourced, or untethered from actual network operations. Readers should treat this as a registry artefact rather than a verified personal profile.

For now, Karamperis remains a thin intelligence lead. The profile is a monitoring baseline Fragnet’s infrastructure dependencies. When the registry record next changes or a BGP event occurs, the relevance of this subject will shift. Until then, his impact is limited to registry coordination and abuse contact response.

Operating Surface

Karamperis is the designated admin and tech contact for AS210365, responsible under RIPE policy for responding to abuse reports, maintaining accurate registry data, and coordinating with the RIPE NCC. This role gives him a public face for the ASN, but internal decision-making authority within Fragnet AB remains unverified.

Registry contacts are operational tripwires. Karamperis's name on AS210365 creates an observable link between a person, an ASN, and a commercial hosting network. Tracking changes to his registry record can signal administrative turnover, network reassignment, or shifts in infrastructure dependencies. Routing activity from the ASN would elevate his monitoring priority.

Watchpoints

Karamperis’s public visibility is entirely contingent on the RIPE RDAP record for AS210365. Any change to that record or the emergence of routing activity would immediately shift the intelligence value of this profile. Currently, the lack of routing data and personal verification caps his relevance.

1. Modification of the IKAR-RIPE handle or the AS210365 admin/tech contact fields. 2) BGP announcements originating from AS210365. 3) Appearance of Ioannis Karamperis in other RIPE handles, PeeringDB, or public events. 4) New company biographies or professional profiles linking him to Fragnet AB.

2. No direct employment verification from Fragnet AB. 2) No personal biography, education history, or nationality. 3) No active prefix or routing sample. 4) No image or distinct online presence. Filling any of these would build a more informative profile.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for Ioannis Karamperis.
• RIPE registry record - RIPEstat identifies AS210365 as FRAGNET and provides public network overview context for the ASN.
• opencorporates.com - OpenCorporates lists Fragnet AB as a Swedish company, supporting the existence of the operator named in ASN registration context.
• fragnet.net - Fragnet publicly presents itself as a hosting provider for game servers and related infrastructure services.