Skip to content

Autonomous System

AS48347MTW-AS(RU)

Last fetched

AS48347 is an Autonomous System operated by MTW-AS and registered in RU. As of Thu, 21 May 2026 01:00:41 GMT, it announces 89 routed IP prefixes and peers with 32 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS48347Routing diversity9.7/10Peering density6.1/10MOAS conflict✓ noneThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/asn/48347

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS8395EAST-ASRU
AS216218DATA-1-ASRU
AS216090SERVICE-VRU
AS214822MTFINANCE-ASRU
AS212490SETIRU
AS210028CSRU
AS207676BEST-LINE-ASRU
AS206764MEDIASOFT-ASRU
AS204623NEWLINE-ASRU
AS199664WEAREWAYRU
AS62444ALTRUMRU
AS62356ITNOVATION-ASRU
AS62255BEMYLINKSI
AS61380ENGINETPLUS-ASRU
AS59692IQWEBAE
AS59584INDIKOM-ASRU
AS57724DDOS-GUARDRU
AS51579CORP-PARTNER-ASRU
AS51009NICOS-MSK Nicos Autonomous SystemRU
AS50668DIALOGK-ASRU
AS50509TRANSROUTERU
AS49863LITE-TELECOM-ASRU
AS49155KETRA-ASRU
AS47258PREMIER-GC-ASRU
AS43865INTEK-M-ASRU
AS43667VRMNT-ASRU
AS42148BEIREL-ASRU
AS41639INCOMSV-ASRU
AS37721Virtual-Technologies-Solutions-SABF
AS35598INETCOMRU
AS24482SGGS-AS-AP SG.GSSG
AS9049ERTH-TRANSIT-ASRU

Blast radius

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

~5,607 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 01:00:41 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS48347.

Cypher and MCP

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

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