Skip to content

Autonomous System

AS41722 — MIRAN-AS Miran DC(RU)

Last fetched

AS41722 is an Autonomous System operated by MIRAN-AS Miran DC and registered in RU. As of Thu, 21 May 2026 10:42:14 GMT, it announces 43 routed IP prefixes and peers with 19 other Autonomous Systems in the WhisperGraph BGP dataset.

Nutrition Label

WHISPER CANON · AS41722Routing diversity8.2/10Peering density5.2/10MOAS conflict✓ noneThreat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/asn/41722

Routing footprint

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

Peering ecosystem

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

Peer ASNOperatorCountry
AS6939HURRICANE - Hurricane Electric LLCUS
AS214367RU-PAYGINERU
AS212165KVMKARU
AS205864EDISOFT-ASRU
AS202989OFIS24RU
AS201706AS-SERVICEPIPERU
AS200172—RU
AS57596ITH-ASRU
AS56923VIRTUALFORT-ASRU
AS56846NSC-ASRU
AS49673TRUENETWORK Truenetwork InfrastructureRU
AS43951GT-LTRU
AS37721Virtual-Technologies-Solutions-SABF
AS31500GNM-ASAG
AS24482SGGS-AS-AP SG.GSSG
AS20764RASCOM-AS CJSC RASCOM ISPRU
AS20485TRANSTELECOM Moscow, RussiaRU
AS12654RIPE-NCC-RIS-AS Reseaux IP Europeens Network Coordination Centre RIPE NCCNL
AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRU

Blast radius

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

~7,719 hostnames depend on this network.Sampled from 10 prefixes, snapshot Thu, 21 May 2026 10:42:14 GMT.

MOAS / hijack watch

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

Threat posture

Related pages

Pivot deeper into the graph from AS41722.

Cypher and MCP

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

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