Autonomous System
AS23576
Last fetched
AS23576 is operated by nhn-AS-KR-KR - NAVER Cloud Corp., registered in KR, and announces 169 prefixes to 15 BGP neighbours. AS23576 has a reputation score of 9.8 (REPUTABLE); 2 of its 126,464 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 169
- BGP neighbours
- 15
- RPKI ROAs
- 37
- MOAS conflicts
- 0
- CAIDA AS-rank
- 7,974
- Customer-cone ASNs
- 2
- Facilities
- 102
- Internet exchanges
- 10
- Customer degree
- 1
- Peer degree
- 152
- Provider degree
- 13
- 1.255.48.0/23
- 1.255.48.0/22
- 1.255.50.0/23
- 1.255.52.0/23
- 1.255.52.0/22
- 1.255.54.0/23
- 1.255.56.0/23
- 1.255.56.0/22
- 1.255.58.0/23
- 1.255.60.0/23
- 1.255.60.0/22
- 1.255.62.0/23
- 38.77.206.0/24
- 43.250.154.0/23
- 49.50.176.0/21
- 49.50.184.0/23
- 49.50.186.0/23
- 49.236.132.0/22
- 49.236.144.0/21
- 61.97.176.0/20
- 61.247.192.0/20
- 61.247.208.0/22
- 61.247.216.0/22
- 61.247.220.0/24
- 61.247.221.0/24
Infrastructure presence
Internet exchanges (10 total)
Facilities (102 total)
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Equinix SV8 - Silicon Valley, Palo Alto
- NIKHEF Amsterdam
- Digital Realty NYC (111 8th Ave)
- Digital Realty NYC (60 Hudson)
- Telehouse - London (Docklands North)
- Telehouse - London (Docklands East)
- Equinix NY2/NY4/NY5/NY6 - New York, Secaucus
- Digital Realty London LHR19
- Digital Realty London LHR20
- Digital Realty London LON1-3
- Equinix LD8 - London, Docklands
- Digital Realty AMS3/5/7/8/10 - Amsterdam
- ITENOS Frankfurt (FRA1)
- Digital Realty Frankfurt FRA1-27
- Global Switch Amsterdam
- Equinix AM7 - Amsterdam, Kuiperberweg
- Digital Realty AMS17 - Amsterdam
- Equinix FR5 - Frankfurt, KleyerStrasse
- Equinix FR7 - Frankfurt, Gutleutstrasse
- Digital Realty London LHR21 (closed)
- Digital Realty Frankfurt FRA28 (Closed)
- Digital Realty AMS9 - Amsterdam
- Telehouse - Frankfurt
- KINX Dogok
Route origin authorizations
A sample of 10 of this network’s 37 ROAs.
- 101.79.64.0/23 · max length /23
- 101.79.66.0/23 · max length /23
- 111.91.136.0/24 · max length /24
- 111.91.137.0/24 · max length /24
- 202.131.28.0/22 · max length /22
- 211.188.46.0/24 · max length /24
- 49.50.176.0/21 · max length /21
- 49.50.184.0/23 · max length /23
- 49.50.186.0/23 · max length /23
- 203.104.160.0/23
Upstreams
The networks that most often share an observed BGP path with AS23576.
Blast radius
- Announced IPv4 addresses
- 126,464
- Threat-listed addresses
- 2
- Threat density
- 0.0016 %
- Routed prefixes
- 169
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 15 of this network’s 15 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- TWELVE99 - Arelion Sweden AB · AS1299
- KDDI - KDDI CORPORATION · AS2516
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- GTT-BACKBONE - GTT Communications Inc. · AS3257
- LEVEL3 - Level 3 Parent, LLC · AS3356
- PCCWG-APAC-HK - PCCW Global (HK) Ltd. · AS3491
- LGDACOM-KR - LG DACOM Corporation · AS3786
- KIXS-AS-KR-KR - Korea Telecom · AS4766
- AS6453 - TATA COMMUNICATIONS (AMERICA) INC · AS6453
- HURRICANE - Hurricane Electric LLC · AS6939
- SINGTEL-AS-AP - Singapore Telecommunications Ltd · AS7473
- SKB-AS-KR - SK Broadband Co Ltd · AS9318
- MEER-AS - meerfarbig GmbH & Co. KG · AS34549
- NBPAP-AS-AP - NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD. · AS135354
Reputation
9.8reputation score (REPUTABLE)
AS23576 (nhn-AS-KR-KR - NAVER Cloud Corp., KR) has a reputation score of 70.7 (REPUTABLE).
- Threat density
- 75.6/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
- NAVER Cloud Corp.
Threat-feed evidence
Related pages
Pivot from AS23576 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.