Skip to content

Autonomous System

AS8517ULAKNET(TR)

Last fetched

AS8517 is an Autonomous System operated by ULAKNET and registered in TR. As of Thu, 21 May 2026 00:57:42 GMT, it announces 38 routed IP prefixes and peers with 27 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS8517Routing diversity7.9/10Peering density5.8/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/8517

Routing footprint

AS8517 announces 38 distinct routed prefixes. The 25-prefix sample below links to per-prefix pages with full conflict and reverse-DNS detail.

Peering ecosystem

27 distinct peers via BGP. The first 27 are listed below.

Peer ASNOperatorCountry
AS1967METU-NET Middle East Technical University Orta Dogu Teknik Universitesi
AS215977TUBITAK-MAM-ASTR
AS213309MARMARA-EDU-NETTR
AS212167PAU-EDU-ASTR
AS211249YILDIZ-EDU-NETTR
AS210690AREL-UNIVERSITY-ASTR
AS207263TUBITAK-BILGEMTR
AS206887MEDENIYET-EDU-NETTR
AS205782TUBITAK-UME-ASTR
AS201632ANADOLU-EDU-ASTR
AS48811ATILIM-ASTR
AS44639ISIKUNTR
AS42626ATAUNI-ASTR
AS31689EMU-ASTR
AS24922HACETTEPETR
AS24614SAKARYA-NET-ASTR
AS21320GEANT_IAS_VRFNL
AS20965GEANT The GEANT IP ServiceNL
AS15843
AS12777OTHERTR
AS12735ASTURKNETTR
AS9095
AS8678ANKARA-NETTR
AS8466BILKENTTR
AS8456ASBOUNTR
AS5474TOBBETU-NETTR
AS2592EGE-AS BILGI ISLEM DAIRE BASKANLIGI DONANIM SUBE MUDURLUGUTR

Blast radius

Approximate count of dependent hostnames if AS8517 disappeared from the routing table.

~58,790 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 00:57:42 GMT.

MOAS / hijack watch

Prefixes routed by AS8517 that another Autonomous System also announces. A non-empty list is one of the strongest BGP-hijack signals available without active probes.

No active MOAS conflicts. Every prefix announced by AS8517 is unique to AS8517 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS8517.

Cypher and MCP

Reproduce the headline metric directly against graph.whisper.security:

MATCH (a:ASN {name: "AS8517"})-[:HAS_NAME]->(n:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(c:COUNTRY)
RETURN a.name AS asn, n.name AS operator, c.name AS country

Or query Whisper from your own LLM workflow via the Whisper MCP server.