Skip to content

Autonomous System

AS6517LAKENETWORKS-AS - LAKENETWORKS(US)

Last fetched

AS6517 is an Autonomous System operated by LAKENETWORKS-AS - LAKENETWORKS and registered in US. As of Wed, 20 May 2026 23:34:06 GMT, it announces 19 routed IP prefixes and peers with 23 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS6517Routing diversity6.5/10Peering density5.5/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/6517

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS6939HURRICANE - Hurricane Electric LLCUS
AS216438HLNETWORKING-ASFR
AS216418FSCD-NETIT
AS216309INVISIONTECH-GROUP-SRLIT
AS215760DISPAISY-AS DisPaisy EnterprisesIT
AS213791XENIAHOSTINGIT
AS213573AS-SOLUZIONEUNOIT
AS212085BRUEGGUS-AS Alexander BruegmannDE
AS208753IT
AS208229MICHELE-ROBERTAZZIIT
AS204092GRIFONFR
AS201815MEGADITTAGB
AS199277UG-ASLV
AS59919BRAINBOXIT
AS47927WIFIWEB Wifiweb Service ProviderIT
AS37707SEY-IX-PEERINGSC
AS35625EUROFIBER-FRANCEFR
AS34019HIVANEFR
AS31561NINE-IXFR
AS24961DE
AS23470RELIABLESITE - ReliableSite.Net LLCUS
AS12779ITGATEIT
AS7087Administracion de Redes Colomsat S.A.CO

Blast radius

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

~131 hostnames depend on this network.Sampled from 10 prefixes, snapshot Wed, 20 May 2026 23:34:06 GMT.

MOAS / hijack watch

Prefixes routed by AS6517 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 AS6517 is unique to AS6517 in the current routing snapshot.

Threat posture

Related pages

Pivot deeper into the graph from AS6517.

Cypher and MCP

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

MATCH (a:ASN {name: "AS6517"})-[: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.