Skip to content

Autonomous System

AS34602 — STARLINK-AS Moscow, Russia(RU)

Last fetched

AS34602 is an Autonomous System operated by STARLINK-AS Moscow, Russia and registered in RU. As of Thu, 21 May 2026 15:23:05 GMT, it announces 30 routed IP prefixes and peers with 24 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS34602Routing diversity7.4/10Peering density5.6/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/34602

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS6939HURRICANE - Hurricane Electric LLCUS
AS208972GIBIRNET-TR
AS203117MTKRU
AS202832PROBANK-ASRU
AS62255BEMYLINKSI
AS59679ARZHI-ASRU
AS58319KAZAKOV-ASRU
AS58072ZENONLINE-ASRU
AS58020TERSYS-ASRU
AS56655GIGAHOSTNO
AS50673SERVERIUS-ASNL
AS49673TRUENETWORK Truenetwork InfrastructureRU
AS49063DTLNRU
AS43727KVANT-TELECOMRU
AS43298STORMNETWORKSRU
AS39238OKBPROGRESS Moscow, RussiaRU
AS37721Virtual-Technologies-Solutions-SABF
AS35598INETCOMRU
AS34927IFOG-GMBHCH
AS30823AUROLOGIC aurologic GmbHDE
AS29076CITYTELECOM-AS Filanco LTDRU
AS24482SGGS-AS-AP SG.GSSG
AS20764RASCOM-AS CJSC RASCOM ISPRU
AS9049ERTH-TRANSIT-ASRU

Blast radius

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

Blast radius: Computing — check back later. The precompute pipeline refreshes this panel within a few days.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS34602.

Cypher and MCP

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

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