Autonomous System
AS9607
Last fetched
AS9607 is operated by BBTower - BroadBand Tower, Inc., registered in JP, and announces 25 prefixes to 16 BGP neighbours. AS9607 has a reputation score of 8.1 (REPUTABLE); 1 of its 31,744 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 25
- BGP neighbours
- 16
- RPKI ROAs
- 27
- MOAS conflicts
- 0
- CAIDA AS-rank
- 1,084
- Customer-cone ASNs
- 35
- Facilities
- 38
- Internet exchanges
- 6
- Customer degree
- 16
- Peer degree
- 10
- Provider degree
- 3
- 103.96.112.0/22
- 124.147.0.0/20
- 124.147.16.0/21
- 124.147.24.0/22
- 124.147.28.0/22
- 202.183.80.0/21
- 203.141.48.0/22
- 203.141.52.0/23
- 203.141.55.0/24
- 203.141.56.0/21
- 203.216.192.0/19
- 208.111.48.0/21
- 210.231.208.0/22
- 211.14.0.0/21
- 211.14.9.0/24
- 211.14.10.0/23
- 211.14.16.0/22
- 211.14.24.0/23
- 211.14.30.0/23
- 218.231.252.0/23
- 2001:370:a::/48
- 2001:370::/40
- 2001:370:6000::/38
- 2001:370::/32
- 2404:c700::/32
Infrastructure presence
Internet exchanges (6 total)
Facilities (38 total)
- Telehouse – TOKYO Otemachi (KDDI Otemachi)
- Equinix TY2 - Tokyo
- NTT DATA Otemachi Bldg
- Digital Edge TYO2 (ComSpace 1) - Tokyo
- AT TOKYO (CC1/CC2)
- NTT DOCOMO BUSINESS OS2 - Osaka (Telepark Dojima Building 2)
- NTT DATA Dojima (building #4)
- COLT in Asia Tokyo Data Center 1 (TDC1)
- Equinix OS1 - Osaka
- Equinix TY4 - Tokyo
- NTT DOCOMO BUSINESS OS3 - Osaka (Telepark Dojima Building 3)
- NTT DOCOMO BUSINESS OS1 - Osaka (Telepark Dojima Building 1)
- Telehouse – OSAKA 1&2
- FRT iDC Okinawa
- Colt DC Tokyo II
- NTT DATA Mitaka DataCenter EAST
- Otemachi Place West Tower (BBTower Shin-Otemachi)
- NTT DOCOMO BUSINESS Tokyo (NW1)
- NTT DOCOMO BUSINESS TK1 - Tokyo (NTT Otemachi)
- AT TOKYO (DC12 NTT DATA Dojima(building #4))
- Equinix TY11 - Tokyo
- Digital Realty Tokyo - NRT10
- Digital Realty Osaka - KIX11
- SCSK netXDC (SI1/SI2/SI3)/NEC Inzai DC
- QTnet Fukuoka Data Center 3(QD3)
Route origin authorizations
A sample of 10 of this network’s 27 ROAs.
- 103.96.112.0/22 · max length /22
- 124.147.0.0/19 · max length /19
- 124.147.0.0/20 · max length /20
- 124.147.16.0/21 · max length /21
- 124.147.24.0/22 · max length /22
- 124.147.28.0/22 · max length /22
- 2001:370:6000::/38 · max length /38
- 2001:370::/32 · max length /32
- 2001:370::/40 · max length /40
- 2001:370:a::/48 · max length /48
Upstreams
The networks that most often share an observed BGP path with AS9607.
Blast radius
- Announced IPv4 addresses
- 31,744
- Threat-listed addresses
- 1
- Threat density
- 0.0032 %
- Routed prefixes
- 20
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 16 of this network’s 16 BGP neighbours.
- IIJ - Internet Initiative Japan Inc. · AS2497
- ASN-TELSTRA-GLOBAL - Telstra Global · AS4637
- HURRICANE - Hurricane Electric LLC · AS6939
- MEDIAWEB - Fujitsu Systems Applications & Support Limited · AS7505
- SYNAPSE - SYNAPSE Co.,Ltd. · AS7511
- BBTower-Lab - BroadBand Tower, Inc. · AS7530
- COLT - COLT Technology Services Group Limited · AS8220
- SHIBATA - Niigata Communication Service · AS9601
- NIRAI - Okinawa Cable Network Inc. · AS24277
- KAMOIKE-NET - Kamoike.net LLP · AS63774
- BIRDIE-NET - dual&Co. Inc. · AS63780
- CA-LAB - CyberAgent, Inc. · AS63790
- WP-NET - Woven by Toyota, Inc. · AS146974
- KNET - Kvision Co.,Ltd. · AS146976
- Nekojarashi - Nekojarashi Inc. · AS146981
- Infal - TelHi Corporation · AS150369
Reputation
8.1reputation score (REPUTABLE)
AS9607 (BBTower - BroadBand Tower, Inc., JP) has a reputation score of 75.8 (REPUTABLE).
- Threat density
- 90.0/100
- Graph metrics
- 80.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
- BroadBand Tower, Inc.
Threat-feed evidence
Related pages
Pivot from AS9607 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.