asn.dev

Observed topology

AS10036 CNM-AS-KR DLIVE

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10036: 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
AS9957KINXHostingIPv415,319
AS3786LG DACOM CorporationUnclassifiedIPv45,997
AS9848SEJONG NETWORKSResidentialIPv43,746
AS6939Hurricane Electric LLCTransitIPv42,709
AS9304HGC Global Communications LimitedHostingIPv4293
AS9457DREAMLINE CO.HostingIPv424

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9943KangNam CableTVResidentialIPv46,778
AS18334Gyounggidongbu cable tv co., Ltd.UnclassifiedIPv41,067

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9957KINXHostingIPv422,356
AS9943KangNam CableTVResidentialIPv46,778
AS3786LG DACOM CorporationUnclassifiedIPv46,355
AS9848SEJONG NETWORKSResidentialIPv44,081
AS6939Hurricane Electric LLCTransitIPv42,725
AS18334Gyounggidongbu cable tv co., Ltd.UnclassifiedIPv41,067
AS9304HGC Global Communications LimitedHostingIPv4392
AS9457DREAMLINE CO.HostingIPv424

Provenance

Where this comes from

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