Autonomous System
AS29124
Last fetched
AS29124 is operated by ISKRATELECOM-AS - Iskratelecom JSC, registered in RU, and announces 50 prefixes to 11 BGP neighbours. AS29124 has a reputation score of 12.2 (NEUTRAL); 32 of its 154,368 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 50
- BGP neighbours
- 11
- RPKI ROAs
- 26
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,519
- Customer-cone ASNs
- 11
- Facilities
- 27
- Internet exchanges
- 6
- Customer degree
- 7
- Peer degree
- 15
- Provider degree
- 3
- 46.31.24.0/21
- 46.39.228.0/23
- 46.39.230.0/23
- 46.39.224.0/19
- 46.39.244.0/22
- 46.39.248.0/23
- 62.182.72.0/21
- 79.172.64.0/18
- 81.200.0.0/24
- 81.200.1.0/24
- 81.200.4.0/24
- 81.200.5.0/24
- 81.200.6.0/24
- 81.200.0.0/20
- 81.200.8.0/24
- 81.200.9.0/24
- 81.200.10.0/23
- 81.200.0.0/19
- 81.200.16.0/23
- 81.200.23.0/24
- 81.200.24.0/24
- 81.200.28.0/22
- 82.199.96.0/23
- 82.199.98.0/23
- 82.199.101.0/24
Infrastructure presence
Internet exchanges (6 total)
Facilities (27 total)
- Equinix FR5 - Frankfurt, KleyerStrasse
- Moscow M9
- Linxdatacenter (Moscow)
- NewTelco Kiev
- CSS MPS Moscow
- Moscow M10
- Moscow CSS MPS
- Bolshaya Morskaya 18
- LVRTC TV Tower
- Telia Telehouse KJJ
- Digita Helsinki Pasila Broadcasting Tower
- NewTelco Frankfurt
- IVC ORW Saint-Petersburg
- Moscow TehnoGorod
- Tsvetochnaya Data Center
- StoreData
- Raduga-2
- M100 datacenter Moscow, Varshavskoe 125
- IXcellerate MOS1
- DataSpace Moscow
- Miran-1
- DataLine Moscow DC NORD
- DataLine Moscow DC OST
- KIAEHOUSE
- INFONET DC
Route origin authorizations
A sample of 10 of this network’s 26 ROAs.
- 109.225.192.0/18 · max length /24
- 109.229.128.0/19 · max length /24
- 134.0.96.0/20 · max length /24
- 176.97.128.0/21 · max length /24
- 185.55.0.0/22 · max length /24
- 185.60.44.0/22 · max length /24
- 188.68.96.0/19 · max length /24
- 195.234.56.0/24 · max length /24
- 213.193.0.0/19 · max length /24
- 2a02:2620::/32 · max length /48
Upstreams
The networks that most often share an observed BGP path with AS29124.
Blast radius
- Announced IPv4 addresses
- 154,368
- Threat-listed addresses
- 32
- Threat density
- 0.0207 %
- Routed prefixes
- 49
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 11 of this network’s 11 BGP neighbours.
- HURRICANE - Hurricane Electric LLC · AS6939
- RASCOM-AS - CJSC RASCOM · AS20764
- SGGS-AS-AP - SG.GS · AS24482
- ISKRATELECOM-AS - Iskratelecom JSC · AS30784
- MF-MGSM-AS - PJSC MegaFon · AS31133
- iFog-GmbH - iFog GmbH · AS34927
- Virtual Technologies & Solutions - Virtual Technologies & Solutions · AS37721
- BUSINESSCENTER-AS - Buisiness Kvartal Nov Ltd. · AS50283
- GYDROZO-AS - LLC "Gydrozo" · AS56678
- Clinic-Aesthetic-Medicine - Clinic-Aesthetic-Medicine · AS56935
- ESKNET - Yedinaya Setevaya Kompaniya Ltd · AS199634
Reputation
12.2reputation score (NEUTRAL)
AS29124 (ISKRATELECOM-AS - Iskratelecom JSC, RU) has a reputation score of 65.6 (NEUTRAL).
- Threat density
- 61.0/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
- Iskratelecom JSC
- RIR
- RIPE
- Registered
- Wed, 11 Jun 2003 07:59:59 GMT
- Abuse contact
- abuse@seven-sky.net
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS29124 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.