Murat KESKIN is a person identified in public RIPE NCC registry records as the admin-c and tech-c for AS210289 (handle MK22954-RIPE). The evidence is limited to RDAP, RIPE Database, and BGP visibility for the ASN; no employer, biography, or routing authority is independently confirmed. The profile provides a human accountability reference for network operations follow-up and abuse escalation. Watchpoints include registry record changes, prefix announcements, and new biographical evidence. Uncertainty: employer and role not verified; the profile is a registry-contact pointer.

Murat KESKIN

Murat KESKIN is the publicly listed administrative and technical contact for autonomous system AS210289 in RIPE NCC registry data, appearing under handle MK22954-RIPE. His registry presence provides an accountable human reference for network operations follow-up, abuse handling, and peering inquiries, though direct operational control or employer affiliation remains unconfirmed.

Why It Matters

A named contact in RIR registration data provides an accountable human reference in public number-resource records, directly affecting network operations follow-up. Changes to Murat KESKIN's registry listing could shift responsibility attribution, alter abuse and peering contact routing, and signal administrative turnover or resource reassignment for AS210289, even without proof of direct routing control.

What Public Sources Show

Murat KESKIN is a publicly listed administrative and technical contact for autonomous system AS210289, registered with RIPE NCC under handle MK22954-RIPE. He appears in registry data as the human point of accountability for network operations inquiries, abuse handling, and peering coordination related to this internet routing resource.

Public records from the RIPE Database and RDAP confirm his role as admin-c and tech-c for AS210289. The autonomous system is externally observable via global BGP monitoring platforms, such as bgp.he.net, confirming its active presence in the internet routing fabric. These official sources provide the sole verified connection between Keskin and the registered number resource.

Keskin’s operational control surface is confined to the registry. He may be authorized to receive abuse reports, manage peering inquiries, or update registry entries, but no public evidence proves he directly manages routing decisions or network infrastructure. The organization that ultimately holds AS210289 remains unnamed in the reviewed sources.

As a named contact in an RIR registration, Keskin’s listing affects how operators and investigators attribute responsibility for AS210289. A change in his registry record—removal, replacement, or update—could shift incident escalation paths and alter the public accountability baseline for the autonomous system’s activities.

Key watchpoints include any update to the RIPE entry for AS210289 that alters Keskin’s contact details. The appearance of BGP-announced prefixes originating from the ASN would provide concrete routing context and could strengthen or weaken the association between the contact and the network’s operations. Discovery of a public employer profile or corporate page would resolve outstanding identity uncertainties.

Uncertainty surrounds Keskin’s actual employer, job title, and operational authority. The evidence does not independently verify his organizational affiliation, biography, or location beyond the registry context. This profile remains a registry-contact pointer rather than a complete personal or corporate dossier, and readers should treat it as a limited public accountability signal.

Operating Surface

Publicly accessible RDAP/WHOIS records for AS210289 show Murat KESKIN in admin-c and tech-c roles, placing him in the operational context of registry-facing coordination for the organisation that holds or manages the autonomous system. His contact visibility shapes how operators, peers, and investigators identify responsible parties for the registered number resource.

Murat KESKIN serves as a human point of contact in RIPE NCC registry data for AS210289, a routable autonomous system visible in global BGP monitoring. Tracking his registry record helps analysts map points of accountability for infrastructure coordination, incident escalation, and abuse management, and provides a signal that can change if the record is updated, removed, or replaced.

Watchpoints

Murat KESKIN functions as a limited human accountability signal for AS210289; his registry listing is the only public link, making any change in his record a potential indicator of administrative shifts or resource reassignment for the autonomous system.

Changes to his RIPE contact details, new BGP-announced prefixes from AS210289, or the emergence of a verified employer profile would materially alter the assessment of his role and the ASN's operational posture.

The identity of the organization holding AS210289 is missing, as are Keskin's official job title, employer, and any proof of direct network control. Additional official or corporate sources are needed to close these gaps.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for Murat KESKIN.
• RIPE registry record - RIPE Database search page for handle MK22954-RIPE provides the public registry object lookup surface for the Murat KESKIN contact identifier.
• bgp.he.net - Public BGP visibility page exists for AS210289, supporting that the ASN is externally observable as an internet routing resource beyond the contact record.