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.
AuteurGrace Ge
Editorial owner accountable for this profile route.
Temps de lecture3 min
Estimated reading time at standard editorial pace.
Publié leJun 02, 2026
Date this profile last entered editorial circulation.
Last updateJun 02, 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.
SujetPublic network contact
Controlled taxonomy label used for this profile route.
HorizonQuarter (30-120d)
Most likely window for material strategy 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.
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.
Core Entity Brief
Core Entity Brief
Entity
Murat KESKIN
Public role
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.
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
3 public source references
Related coverage
Profile anchor article
Website
Public evidence pending
Last update
Jun 02, 2026
Murat KESKIN appears in external numbering or routing evidence for AS210289; the public assessment is bounded by that source-backed context.
What It Does
Visible operating role: Publicly accessible RDAP/WHOIS records for AS210289 show Murat KESKIN as an admin-c and tech-c style contact in internet number-resource registration context. This places him in the operating context of network administration or registry-facing coordination for the organisation that holds or manages AS210289.
Revenue and customer gap: No supplied evidence establishes a revenue model, customer base, or contract position; those claims need official, financial, or service-source support before publication.
Operating Snapshot
Identity baseline: Murat KESKIN is a named person appearing in RIPE/rdap-published registration data for autonomous system AS210289. Public registry data shows the RIPE entity handle MK22954-RIPE and lists him in administrative and technical contact roles tied to the registered resource holder.
Routing context: No active prefix sample is present in the current evidence set, so the public assessment is limited to ASN identity until routing evidence changes.
Control Surface
Numbering records: The verifiable public control surface is limited to registry-contact visibility around AS210289 and the associated RIPE entity record. Public evidence supports that his name is attached to administrative and technical contact functions in registry data, which can influence how operators, peers, or investigators identify responsible parties for the registered network resource.
Evidence changes: New announcements, withdrawals, or reassigned prefixes attached to AS210289 can change how much operational significance readers should assign to Murat KESKIN.
Watchpoints
Record freshness: Stale, conflicting, or changed public records are the main uncertainty when translating source evidence into an operating profile.
Footprint change: New ASN, prefix, official website, PeeringDB, or registry evidence would raise or lower Murat KESKIN's infrastructure relevance.
Domain of operation
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.
Public role: Murat KESKIN is framed by 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. and public infrastructure context. Evidence basis: Registry RDAP / WHOIS record; RIPE registry record
Operating surface: Public network contact and Europe provide the public context for this institution profile. Evidence basis: Registry RDAP / WHOIS record; RIPE registry record
Timeline
Murat KESKIN public profile updated
Public coverage records Murat KESKIN as a subject for role, operating context, and evidence review.
Signal Map
Signal Map
Why tracked: 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.
Object role: 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.
Impact note: 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.
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 Murat KESKIN 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 Murat KESKIN included?
Murat KESKIN 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.
