Autonomous System
AS9924
Last fetched
AS9924 is operated by TFN-TW - Taiwan Fixed Network, Telco and Network Service Provider., registered in TW, and announces 639 prefixes to 69 BGP neighbours. AS9924 has a reputation score of 10.9 (NEUTRAL); 28 of its 1,892,096 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 639
- BGP neighbours
- 69
- RPKI ROAs
- 186
- MOAS conflicts
- 0
- CAIDA AS-rank
- 669
- Customer-cone ASNs
- 67
- Facilities
- 48
- Internet exchanges
- 10
- Customer degree
- 56
- Peer degree
- 47
- Provider degree
- 10
- 2.18.16.0/23
- 2.21.16.0/22
- 23.202.124.0/22
- 23.212.60.0/24
- 43.240.24.0/22
- 49.214.0.0/16
- 49.214.0.0/15
- 49.215.0.0/16
- 49.216.0.0/16
- 49.217.0.0/16
- 49.216.0.0/14
- 49.218.0.0/16
- 49.219.0.0/16
- 60.198.31.0/24
- 60.198.0.0/17
- 60.198.64.0/18
- 60.198.0.0/16
- 60.198.128.0/20
- 60.198.144.0/21
- 60.198.160.0/19
- 60.198.128.0/17
- 60.198.192.0/24
- 60.198.193.0/24
- 60.198.194.0/24
- 60.198.195.0/24
Routing posture
- Hijack posture score
- 0.08
- Route leaks
- 4
Leak types observed: TYPE2_LATERAL_PEER_TO_PEER, TYPE4_PEER_TO_PROVIDER.
Signals
- critical-infrastructureServes infrastructure the internet depends on operationally.
Infrastructure presence
Internet exchanges (10 total)
Facilities (48 total)
- Equinix SV8 - Silicon Valley, Palo Alto
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Telehouse – TOKYO Otemachi (KDDI Otemachi)
- Equinix TY1 - Tokyo
- Equinix HK1 - Hong Kong
- MEGA-i (iAdvantage Hong Kong)
- Equinix SG1 - Singapore
- CoreSite - Los Angeles (LA2)
- Equinix TY2 - Tokyo
- Equinix SV6 - Silicon Valley, Sunnyvale
- NTT DATA Otemachi Bldg
- Digital Edge TYO2 (ComSpace 1) - Tokyo
- Equinix SG2 - Singapore
- AT TOKYO (CC1/CC2)
- CUHK
- Equinix HK2 - Hong Kong
- Equinix TY3 - Tokyo
- COLT in Asia Tokyo Data Center 1 (TDC1)
- Equinix TY4 - Tokyo
- Equinix SG3 - Singapore
- MEGA Two (iAdvantage Hong Kong)
- Equinix TY8 - Tokyo
- Equinix TY9 - Tokyo
- Equinix TY10 - Tokyo
- Equinix TY5 - Tokyo
Route origin authorizations
A sample of 10 of this network’s 186 ROAs.
- 103.123.189.0/24 · max length /24
- 103.123.190.0/24 · max length /24
- 103.224.132.0/22 · max length /24
- 103.224.192.0/22 · max length /22
- 106.1.0.0/16 · max length /16
- 114.198.160.0/20 · max length /20
- 114.198.176.0/20 · max length /20
- 118.232.0.0/15 · max length /15
- 118.232.0.0/18 · max length /18
- 118.232.0.0/19 · max length /19
Upstreams
The networks that most often share an observed BGP path with AS9924.
Blast radius
- Announced IPv4 addresses
- 1,892,096
- Threat-listed addresses
- 28
- Threat density
- 0.0015 %
- Routed prefixes
- 629
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 69 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- LEVEL3 - Level 3 Parent, LLC · AS3356
- PCCWG-APAC-HK - PCCW Global (HK) Ltd. · AS3491
- MIS-AS - Micron Technology, Inc. · AS3911
- ASN-TELSTRA-GLOBAL - Telstra Global · AS4637
- STARHUB-INTERNET - StarHub Ltd · AS4657
- SEEDNET - Digital United Inc. · AS4780
- PAGICNET-AS1 - PAGIC.net , INC. · AS4781
- SYSNET-AS1 - SYSTEX CORPORATION · AS4783
- HURRICANE - Hurricane Electric LLC · AS6939
- SINGTEL-AS-AP - Singapore Telecommunications Ltd · AS7473
- TWIX - Data Communication Business Group · AS7481
- GLOBALTRANSIT-SC-TW - Savecom International Inc. · AS7533
- TWAREN-TW - National Center for High-performance Computing · AS7539
- MTS - MTS PJSC · AS8359
- RETN-AS - RETN Limited · AS9002
- PUNET-AP - PUNET Taiwan · AS9216
- HUTCHISON-AS-AP - HGC Global Communications Limited · AS9304
- TWGATE-AP - Taiwan Internet Gateway · AS9505
- TRADEVAN-AS-AP - Trade-Van Informaiton Services Co. · AS9671
- SAVECOM-TW - SaveCom Internation Inc. · AS9676
- EASPNET-AS-AP - EASPNET Inc. · AS10135
- ARYAKA-ARIN - Aryaka Networks, Inc. · AS11179
- FLAG-AS - Flag Telecom UK Limited · AS15412
Reputation
10.9reputation score (NEUTRAL)
AS9924 (TFN-TW - Taiwan Fixed Network, Telco and Network Service Provider., TW) has a reputation score of 68.1 (NEUTRAL).
- Threat density
- 78.9/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 60.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
Threat-feed evidence
Related pages
Pivot from AS9924 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.