asn.dev

Observed topology

AS23576 nhn-AS-KR-KR - NAVER Cloud Corp.

Hosting APNIC

Upstreams 41 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 43
Adjacent (IPv6) 0
Upstream graph Who carries AS23576, and who carries them, drawn as a map up to the transit-free core. 9 exchanges Where AS23576 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 41

Networks observed carrying traffic for AS23576: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv41,423
AS174Cogent Communications, LLCTransitIPv4892
AS1299Arelion Sweden ABTransitIPv4833
AS6939Hurricane Electric LLCTransitIPv4801
AS2516KDDI CORPORATIONMobileIPv4629
AS3356Level 3 Parent, LLCTransitIPv4596
AS9318SK Broadband Co LtdUnclassifiedIPv4574
AS3786LG DACOM CorporationUnclassifiedIPv4478
AS3257GTT Communications Inc.TransitIPv4435
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4424

Transit

Downstream networks

inferred

Networks for which AS23576 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS135354NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD.UnclassifiedIPv44,005

Adjacency

Adjacent networks

All 43

Every AS seen directly next to AS23576 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS135354NAVER BUSINESS PLATFORM ASIA PACIFIC PTE. LTD.UnclassifiedIPv44,005
AS2914NTT America, Inc.TransitIPv42,662
AS2516KDDI CORPORATIONMobileIPv41,867
AS174Cogent Communications, LLCTransitIPv41,080
AS1299Arelion Sweden ABTransitIPv41,029
AS6939Hurricane Electric LLCTransitIPv4954
AS3356Level 3 Parent, LLCTransitIPv4867
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4758
AS9318SK Broadband Co LtdUnclassifiedIPv4580
AS3257GTT Communications Inc.TransitIPv4520

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.