Autonomous System
AS43873
Last fetched
AS43873 is operated by AB-AS - Bazovaya Set LLP, registered in KZ, and announces 34 prefixes to 3 BGP neighbours. AS43873 has a reputation score of 14.5 (NEUTRAL).
Nutrition Label
Routing footprint
- Announced prefixes
- 34
- BGP neighbours
- 3
- RPKI ROAs
- 0
- MOAS conflicts
- 0
- Facilities
- 0
- Internet exchanges
- 0
- 46.255.148.0/22
- 46.255.152.0/22
- 46.255.152.0/21
- 46.255.156.0/22
- 46.255.160.0/21
- 46.255.168.0/21
- 46.255.176.0/21
- 46.255.184.0/24
- 79.140.48.0/20
- 79.140.56.0/21
- 79.140.64.0/20
- 79.140.80.0/20
- 79.140.96.0/22
- 79.140.100.0/24
- 79.140.101.0/24
- 79.140.102.0/23
- 79.140.104.0/23
- 79.140.106.0/24
- 79.140.107.0/24
- 79.140.108.0/23
- 79.140.110.0/23
- 79.140.112.0/20
- 79.140.128.0/20
- 79.140.146.0/24
- 79.140.146.0/23
Upstreams
The networks that most often share an observed BGP path with AS43873.
Blast radius
Blast radius is temporarily unavailable.
The threat-density procedure returned no result for this ASN. Refresh in a moment to retry — fresh data is fetched on the next visit.
Peering ecosystem
A sample of 3 of this network’s 3 BGP neighbours.
- KAR-TEL-AS - Kar-Tel LLC · AS21299
- TTC-AS - JSC Transtelecom · AS41798
- D-CLOUD-AS - TemirLanNet LLC · AS202293
Reputation
14.5reputation score (NEUTRAL)
AS43873 (AB-AS - Bazovaya Set LLP, KZ) has a reputation score of 60.9 (NEUTRAL).
- Threat density
- 65.5/100
- Graph metrics
- 55.0/100
- Historical behaviour
- 85.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
- Bazovaya Set LLP
- RIR
- RIPE
- Registered
- Fri, 12 Oct 2007 09:10:29 GMT
- Abuse contact
- info@ab-group.biz
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS43873 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.