asn.dev

Observed topology

AS7562 HCNSEOCHO-AS-KR HCN Dongjak

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7562: 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
AS4766Korea TelecomMobileIPv45,889
AS3786LG DACOM CorporationUnclassifiedIPv42,350
AS9848SEJONG NETWORKSResidentialIPv457
AS9318SK Broadband Co LtdUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS23584PUSAN CABLE TV SYSTEM CO., LTD.UnclassifiedIPv417,745
AS9319HCN CHUNGBUK CABLE TV SYSTEMSResidentialIPv412,587
AS9762kt HCN Co.,Ltd.ResidentialIPv46,882
AS7623Gyeongbuk Cable TVResidentialIPv45,208
AS9569SEOCHO CABLE SYSTEMS CO., LTD.ResidentialIPv44,999
AS9981Saero Network Service LTDResidentialIPv44,964
AS10175Kumho CableResidentialIPv43,162
AS139648PacketStream KoreaHostingIPv49

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS4766Korea TelecomMobileIPv451,282
AS23584PUSAN CABLE TV SYSTEM CO., LTD.UnclassifiedIPv417,745
AS9319HCN CHUNGBUK CABLE TV SYSTEMSResidentialIPv412,587
AS9762kt HCN Co.,Ltd.ResidentialIPv46,882
AS3786LG DACOM CorporationUnclassifiedIPv46,825
AS9848SEJONG NETWORKSResidentialIPv45,736
AS7623Gyeongbuk Cable TVResidentialIPv45,208
AS9569SEOCHO CABLE SYSTEMS CO., LTD.ResidentialIPv44,999
AS9981Saero Network Service LTDResidentialIPv44,964
AS10175Kumho CableResidentialIPv43,162

All 12 adjacent →

Provenance

Where this comes from

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