asn.dev

Observed topology

AS45974 NHN-AS-KR NHNCLOUD

Hosting ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45974: 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
AS9318SK Broadband Co LtdUnclassifiedIPv49,628
AS2914NTT America, Inc.TransitIPv46,133
AS3786LG DACOM CorporationUnclassifiedIPv45,362
AS4637Telstra GlobalUnclassifiedIPv41,586
AS151386NHN Cloud Japan CorporationUnclassifiedIPv461

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9636NHNPaycoUnclassifiedIPv461
AS10038NHNCLOUDHostingIPv460
AS10157NHN BugsUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9318SK Broadband Co LtdUnclassifiedIPv49,643
AS2914NTT America, Inc.TransitIPv46,156
AS3786LG DACOM CorporationUnclassifiedIPv45,425
AS4637Telstra GlobalUnclassifiedIPv41,608
AS9636NHNPaycoUnclassifiedIPv461
AS151386NHN Cloud Japan CorporationUnclassifiedIPv461
AS10038NHNCLOUDHostingIPv460
AS10157NHN BugsUnclassifiedIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.