Autonomous System
AS23688
Last fetched
AS23688 is operated by LINK3-TECH-AS-BD-AP - Link3 Technologies Ltd., registered in BD, and announces 282 prefixes to 50 BGP neighbours. AS23688 has a reputation score of 12.7 (NEUTRAL); 198 of its 53,760 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 282
- BGP neighbours
- 50
- RPKI ROAs
- 1,448
- MOAS conflicts
- 0
- CAIDA AS-rank
- 865
- Customer-cone ASNs
- 48
- Facilities
- 4
- Internet exchanges
- 4
- Customer degree
- 47
- Peer degree
- 1
- Provider degree
- 7
- 27.147.128.0/24
- 27.147.129.0/24
- 27.147.130.0/24
- 27.147.131.0/24
- 27.147.132.0/24
- 27.147.133.0/24
- 27.147.134.0/24
- 27.147.135.0/24
- 27.147.136.0/24
- 27.147.137.0/24
- 27.147.138.0/24
- 27.147.139.0/24
- 27.147.140.0/24
- 27.147.141.0/24
- 27.147.142.0/24
- 27.147.143.0/24
- 27.147.128.0/19
- 27.147.144.0/24
- 27.147.145.0/24
- 27.147.144.0/22
- 27.147.146.0/24
- 27.147.147.0/24
- 27.147.148.0/24
- 27.147.149.0/24
- 27.147.150.0/24
Infrastructure presence
Internet exchanges (4 total)
Route origin authorizations
A sample of 10 of this network’s 1,448 ROAs.
- 103.141.66.0/23 · max length /24
- 103.197.152.0/22 · max length /24
- 103.230.40.0/23 · max length /24
- 103.232.100.0/22 · max length /24
- 103.44.151.0/24 · max length /24
- 123.200.0.0/19 · max length /24
- 163.47.32.0/22 · max length /24
- 203.76.96.0/19 · max length /24
- 2400:ca00:100::/48 · max length /48
- 2400:ca00:1f1::/48 · max length /48
Upstreams
The networks that most often share an observed BGP path with AS23688.
Blast radius
- Announced IPv4 addresses
- 53,760
- Threat-listed addresses
- 198
- Threat density
- 0.3683 %
- Routed prefixes
- 268
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 25 of this network’s 50 BGP neighbours.
- THECITYBANK-BD - Jibon Bima Tower (4th Floor) · AS9651
- BIGMEDIALIMITED-AS-AP - Big Media Limited · AS24382
- MTBSYSADMIN-BD - Head Office · AS55344
- DBBL-BD - Dutch-Bangla Bank Limited, Your Trusted Partner · AS58445
- CYBERGATE-BD - Cybergate Limited · AS58599
- LEVEL3-BD - Level3 Carrier Ltd. · AS58682
- UNICEF-BD - Unicef Bangladesh, · AS58695
- EARTHTELECOMMUNICATION-AS - EARTH TELECOMMUNICATION (Pvt) LTD. · AS58715
- SUMMITCOMMUNICATIONS-BD - Summit Communications Ltd · AS58717
- BANKASIALIMITED-AS-AP - Bank Asia Limited · AS58814
- LANKABANGLA-BD - LankaBangla Information System Limited · AS58935
- SEBL-BD - Eunoos Trade Center · AS59321
- DESCO-AS-AP - Dhaka Electric Supply Company Limited (DESCO) · AS59361
- BANKALFALAHLTD-AS-AP - Bank Alfalah Ltd. · AS63851
- TAHOECOM-AS-AP - Tahoe Communication Limited · AS132436
- BANGLADESH-AS-AP - Bangladesh Submarine Cable Company Limited (BSCCL) · AS132602
- BEES-AS-AP - Bangladesh Extension Education Services · AS133083
- IHELPBD-AS-AP - iHelpBD · AS133439
- BRAC-AS - ASN of BRAC · AS133610
- QUANTUMFOUNDATION-AS-AP - Quantum Foundation · AS134403
- BEACON-AS-AP - BEACON PHARMACEUTICALS PLC · AS135101
- TADL-AS-AP - Trust Axiata Digital Limited · AS135378
- EGMCL-AS-AP - Dinesh Gopi Virwani · AS136426
- ABBANK-AS-AP - AB Bank Limited · AS136512
- NBB-AS-AP - NCC Bank, Bangladesh · AS136813
Reputation
12.7reputation score (NEUTRAL)
AS23688 (LINK3-TECH-AS-BD-AP - Link3 Technologies Ltd., BD) has a reputation score of 64.7 (NEUTRAL).
- Threat density
- 51.2/100
- Graph metrics
- 90.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
- Link3 Technologies Limited
- RIR
- APNIC
- Registered
- Thu, 04 Sep 2008 06:40:35 GMT
- Abuse contact
- ngnc@link3.net
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS23688 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.