Autonomous System
AS17511
Last fetched
AS17511 is operated by OPTAGE - OPTAGE Inc., registered in JP, and announces 68 prefixes to 18 BGP neighbours. AS17511 has a reputation score of 9.2 (REPUTABLE); 40 of its 2,994,432 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 68
- BGP neighbours
- 18
- RPKI ROAs
- 41
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,482
- Customer-cone ASNs
- 11
- Facilities
- 129
- Internet exchanges
- 15
- Customer degree
- 10
- Peer degree
- 41
- Provider degree
- 4
- 58.70.0.0/16
- 58.189.176.0/20
- 58.188.0.0/14
- 59.190.0.0/16
- 60.56.0.0/16
- 60.57.0.0/17
- 60.57.128.0/17
- 61.122.240.0/20
- 61.195.96.0/19
- 61.205.0.0/20
- 61.205.80.0/20
- 61.205.96.0/20
- 61.205.112.0/20
- 61.213.128.0/20
- 101.140.0.0/14
- 103.65.208.0/22
- 103.84.124.0/22
- 103.95.206.0/24
- 103.97.232.0/22
- 103.97.236.0/22
- 103.99.124.0/22
- 103.112.180.0/22
- 103.116.152.0/22
- 103.124.200.0/22
- 103.142.132.0/23
Infrastructure presence
Internet exchanges (15 total)
Facilities (129 total)
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- NIKHEF Amsterdam
- CoreSite - Los Angeles (LA1) One Wilshire
- CoreSite - San Jose (SV1)
- Equinix LA1 - Los Angeles
- Telehouse - London (Docklands North)
- Telehouse - London (Docklands East)
- Digital Realty London LHR20
- Digital Realty London LHR19
- Equinix LD8 - London, Docklands
- Digital Realty London LON1-3
- Global Switch Amsterdam
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- Digital Realty Frankfurt FRA1-27
- ITENOS Frankfurt (FRA1)
- Equinix FR5 - Frankfurt, KleyerStrasse
- Digital Realty AMS17 - Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Digital Realty London LHR21 (closed)
- Equinix FR7 - Frankfurt, Gutleutstrasse
- Digital Realty AMS9 - Amsterdam
- Telehouse - Frankfurt
- Digital Realty Frankfurt FRA28 (Closed)
- Telehouse – TOKYO Otemachi (KDDI Otemachi)
- Equinix TY1 - Tokyo
Route origin authorizations
A sample of 10 of this network’s 41 ROAs.
- 101.140.0.0/14 · max length /32
- 103.84.124.0/22 · max length /32
- 112.68.0.0/14 · max length /32
- 119.228.0.0/14 · max length /32
- 121.80.0.0/14 · max length /32
- 121.84.0.0/14 · max length /32
- 122.100.24.0/21 · max length /32
- 128.22.0.0/16 · max length /32
- 128.27.0.0/16 · max length /32
- 150.66.0.0/16 · max length /32
Upstreams
The networks that most often share an observed BGP path with AS17511.
Blast radius
- Announced IPv4 addresses
- 2,994,432
- Threat-listed addresses
- 40
- Threat density
- 0.0013 %
- Routed prefixes
- 66
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 18 of this network’s 18 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- IIJ - Internet Initiative Japan Inc. · AS2497
- LEVEL3 - Level 3 Parent, LLC · AS3356
- ASN-TELSTRA-GLOBAL - Telstra Global · AS4637
- INTEC - INTEC Inc. · AS4711
- RETN-AS - RETN Limited · AS9002
- Finder - OPTAGE Inc. · AS9358
- ITGATE - IT.Gate S.p.A. · AS12779
- CRC-KCC - CRC Solutions Corp., · AS24270
- KIR - KAGOYA JAPAN Inc. · AS24282
- MYLOC-AS - WIIT AG · AS24961
- VCIU-NET-AS - Value Core Inc. · AS38633
- LWLCOM - LWLcom GmbH · AS50629
- FNC-O2 - NRI SecureTechnologies, Ltd. · AS59118
- KYOTO-PREF - KYOTO Prefectural Government · AS59124
- UCDP-ORLCORP - Universal Orlando · AS63402
- KAP-NET - Kansai Airports · AS131924
- NCJ - OPTAGE Inc. · AS151379
Reputation
9.2reputation score (REPUTABLE)
AS17511 (OPTAGE - OPTAGE Inc., JP) has a reputation score of 72.4 (REPUTABLE).
- Threat density
- 80.3/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 75.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
- OPTAGE Inc.
Threat-feed evidence
Related pages
Pivot from AS17511 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.