Autonomous System
AS41722
Last fetched
AS41722 is operated by MIRAN-AS - Miran Ltd., registered in RU, and announces 43 prefixes to 18 BGP neighbours. AS41722 has a reputation score of 13.6 (NEUTRAL); 17 of its 10,496 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 43
- BGP neighbours
- 18
- RPKI ROAs
- 48
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,364
- Customer-cone ASNs
- 12
- Facilities
- 28
- Internet exchanges
- 4
- Customer degree
- 11
- Peer degree
- 731
- Provider degree
- 4
- 91.142.80.0/24
- 91.142.81.0/24
- 91.142.82.0/24
- 91.142.83.0/24
- 91.142.84.0/24
- 91.142.85.0/24
- 91.142.86.0/24
- 91.142.87.0/24
- 91.142.90.0/24
- 91.142.91.0/24
- 91.142.92.0/24
- 91.142.93.0/24
- 91.142.94.0/24
- 91.142.95.0/24
- 178.249.68.0/24
- 178.249.69.0/24
- 178.249.70.0/24
- 178.249.71.0/24
- 178.250.152.0/24
- 178.250.153.0/24
- 178.250.154.0/24
- 178.250.155.0/24
- 185.53.20.0/24
- 185.53.21.0/24
- 185.53.22.0/24
Infrastructure presence
Internet exchanges (4 total)
Facilities (28 total)
- Moscow M9
- Linxdatacenter (Moscow)
- CSS MPS Moscow
- Moscow CSS MPS
- Moscow M10
- Bolshaya Morskaya 18
- LVRTC TV Tower
- Telia Telehouse KJJ
- Digita Helsinki Pasila Broadcasting Tower
- IVC ORW Saint-Petersburg
- Telehouse Saint Petersburg
- Tsvetochnaya Data Center
- Moscow TehnoGorod
- StoreData
- Raduga-2
- M100 datacenter Moscow, Varshavskoe 125
- IXcellerate MOS1
- DataSpace Moscow
- Miran-1
- Miran-2
- RETNNet OV DC
- DataLine Moscow DC NORD
- DataLine Moscow DC OST
- KIAEHOUSE
- Prometey Ltd SPB MM11
Route origin authorizations
A sample of 10 of this network’s 48 ROAs.
- 178.249.68.0/24 · max length /24
- 178.249.69.0/24 · max length /24
- 178.249.70.0/24 · max length /24
- 178.249.71.0/24 · max length /24
- 178.250.152.0/24 · max length /24
- 178.250.153.0/24 · max length /24
- 178.250.154.0/24 · max length /24
- 178.250.155.0/24 · max length /24
- 185.147.80.0/24 · max length /24
- 185.147.81.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS41722.
Blast radius
- Announced IPv4 addresses
- 10,496
- Threat-listed addresses
- 17
- Threat density
- 0.1620 %
- Routed prefixes
- 41
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.
Peering ecosystem
A sample of 18 of this network’s 18 BGP neighbours.
- HURRICANE - Hurricane Electric LLC · AS6939
- ROSTELECOM-AS - PJSC Rostelecom · AS12389
- RIPE-NCC-RIS-AS - Reseaux IP Europeens Network Coordination Centre (RIPE NCC) · AS12654
- TRANSTELECOM - Joint Stock Company TransTeleCom · AS20485
- RASCOM-AS - CJSC RASCOM · AS20764
- SGGS-AS-AP - SG.GS · AS24482
- Virtual Technologies & Solutions - Virtual Technologies & Solutions · AS37721
- GT-LT - LLC "Lanit-Tercom" · AS43951
- TRUENETWORK - Truenetwork LLC · AS49673
- NSC-AS - JSC National satellite company · AS56846
- VIRTUALFORT-AS - Virtualfort OOO · AS56923
- ITH-AS - ITH Ltd. · AS57596
- AS-SERVICEPIPE - SERVICEPIPE LLC · AS201706
- UFO-TECHNOLOGIES-LIMITED - UFO TECHNOLOGIES LIMITED · AS201738
- Edisoft-AS - Ediweb LLC · AS205864
- kvmka - Alex Group LLC · AS212165
- RU-PAYGINE - JSC "Pay Engine" · AS214367
- RDPTERM-AS - Lisitsina Elena Yurievna · AS218988
Reputation
13.6reputation score (NEUTRAL)
AS41722 (MIRAN-AS - Miran Ltd., RU) has a reputation score of 62.8 (NEUTRAL).
- Threat density
- 52.9/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 75.0/100
- Prefix age
- 20.0/100
These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.
Registration
- Registered to
- Miran Ltd.
- RIR
- RIPE
- Registered
- Fri, 13 Oct 2006 14:21:32 GMT
- Abuse contact
- abuse@miran.ru
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS41722 into the prefixes, peers and country it routes for.
Queries
This ASN's full card — routing footprint, peers, conflicts and RIR facts.
MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
collect(an.name) AS operatorNames,
collect(co.name) AS countries,
collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
a.rir AS rir,
a.orgName AS orgName,
a.asRank AS asRank,
a.coneAsns AS coneAsns,
a.conePrefixes AS conePrefixes,
a.coneAddresses AS coneAddresses,
a.registrationDate AS registrationDate,
a.reputationScore AS reputationScore,
a.reputationCategory AS reputationCategory,
a.overallThreatLevel AS overallThreatLevel,
a.abuseEmail AS abuseEmail,
a.hijackPostureScore AS hijackPostureScore,
a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
a.routeLeakCount AS routeLeakCount,
a.routeLeakTypes AS routeLeakTypes,
a.degreeCustomer AS degreeCustomer,
a.degreePeer AS degreePeer,
a.degreeProvider AS degreeProvider,
operatorNames, countries, organizations,
samplePrefixes, samplePeers, sampleConflicts,
signals, sampleExchanges, sampleFacilities, sampleRoas,
prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCountRun yourself →The five networks that most often share this ASN's observed BGP paths.
MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.