Autonomous System
AS10010
Last fetched
AS10010 is operated by TOKAI - TOKAI Communications Corporation, registered in JP, and announces 192 prefixes to 36 BGP neighbours. AS10010 has a reputation score of 7.7 (REPUTABLE).
Nutrition Label
Routing footprint
- Announced prefixes
- 192
- BGP neighbours
- 36
- RPKI ROAs
- 159
- MOAS conflicts
- 0
- Facilities
- 44
- Internet exchanges
- 6
- 27.97.216.0/24
- 27.97.217.0/24
- 27.120.0.0/18
- 27.120.64.0/18
- 27.120.128.0/20
- 27.120.144.0/20
- 42.122.232.0/21
- 42.122.240.0/21
- 42.122.248.0/23
- 42.122.250.0/23
- 42.122.252.0/22
- 42.123.32.0/22
- 42.123.64.0/19
- 42.123.103.0/24
- 42.123.104.0/24
- 42.123.106.0/24
- 42.123.107.0/24
- 42.123.108.0/24
- 42.123.96.0/19
- 42.123.114.0/24
- 42.123.117.0/24
- 42.123.118.0/24
- 42.123.120.0/24
- 42.123.120.0/21
- 42.123.125.0/24
Infrastructure presence
Internet exchanges (6 total)
Facilities (44 total)
- Telehouse – TOKYO Otemachi (KDDI Otemachi)
- Equinix TY1 - Tokyo
- 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)
- Equinix TY3 - Tokyo
- COLT in Asia Tokyo Data Center 1 (TDC1)
- Equinix OS1 - Osaka
- Equinix TY4 - Tokyo
- Telehouse – OSAKA 1&2
- Equinix TY7 - Tokyo
- Equinix TY8 - Tokyo
- Equinix TY9 - Tokyo
- Equinix TY5 - Tokyo
- Equinix TY6 - Tokyo
- Equinix TY10 - Tokyo
- 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)
Route origin authorizations
A sample of 10 of this network’s 159 ROAs.
- 103.139.250.0/23 · max length /24
- 103.26.34.0/24 · max length /24
- 110.172.56.0/21 · max length /24
- 111.67.112.0/21 · max length /24
- 111.67.120.0/22 · max length /24
- 111.67.124.0/22 · max length /24
- 112.137.192.0/18 · max length /24
- 112.138.0.0/17 · max length /24
- 112.138.128.0/17 · max length /24
- 112.139.0.0/17 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS10010.
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 25 of this network’s 36 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- TWELVE99 - Arelion Sweden AB · AS1299
- IIJ - Internet Initiative Japan Inc. · AS2497
- BIGLOBE - BIGLOBE Inc. · AS2518
- ASN-TELSTRA-GLOBAL - Telstra Global · AS4637
- FINE - Canon IT Solutions Inc. · AS4678
- MIRAI - Mirai Communication Network Inc. · AS7690
- RETN-AS - RETN Limited · AS9002
- NIandC - Nippon Information and Communication Corporation · AS9990
- CONVERGE-AS - Converge ICT Solutions Inc. · AS17639
- GIGAINFRA - SoftBank Corp. · AS17676
- WIND - Gunma Internet Co,.ltd · AS17678
- WINTECH-COM - Wingtechnology Communications, Inc. · AS17683
- S-UTOPIA - SAKURA KCS Corporation. · AS17947
- ICO - BroadBand Security, Inc. · AS17953
- C-able - Yamaguchi Cable Vision Co.,Ltd · AS18077
- ntt-bizlink - NTT Bizlink, Inc. · AS23639
- OBIS - OBIS · AS23642
- SUNFIELD - SUN FIELD INTERNET LIMITED · AS23785
- LCV - LCV Corporation · AS23791
- FURUKAWA - Fitec Corp. · AS23795
- RELNET - RELATION Co., Ltd. · AS23836
- JPIX-64ES - Japan Internet Xing Co., Ltd. · AS24257
- YOSHIZOU - Yoshizou XYZ Solutions · AS38642
- DA - Digital Alliance Co.,Ltd. · AS55385
Reputation
7.7reputation score (REPUTABLE)
AS10010 (TOKAI - TOKAI Communications Corporation, JP) has a reputation score of 76.9 (REPUTABLE).
- Threat density
- 86.1/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.
Threat-feed evidence
Related pages
Pivot from AS10010 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.