asn.dev

Observed topology

AS10158 KAKAO-10158-AS-KR-KR - Kakao Corp

Hosting APNIC

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS10158: 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
AS3491PCCW Global (HK) Ltd.TransitIPv4607
AS1299Arelion Sweden ABTransitIPv4 IPv6500
AS9318SK Broadband Co LtdUnclassifiedIPv4 IPv6288
AS4637Telstra GlobalUnclassifiedIPv4 IPv6101
AS6939Hurricane Electric LLCTransitIPv432
AS24482SG.GSHostingIPv47
AS1836green.ch AGResidentialIPv44
AS6797GlobalConnect ABUnclassifiedIPv44
AS29169GANDI SASHostingIPv44
AS48362Stadtwerke FeldkirchResidentialIPv44

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS38099Kakao CorpUnclassifiedIPv4 IPv63,142
AS7625Kakao CorpHostingIPv4 IPv62,347
AS18160Kakao CorpUnclassifiedIPv4 IPv61,473
AS152199Kakao CorpUnclassifiedIPv4 IPv61,351

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv66,781
AS38099Kakao CorpUnclassifiedIPv4 IPv63,142
AS7625Kakao CorpHostingIPv4 IPv62,347
AS18160Kakao CorpUnclassifiedIPv4 IPv61,473
AS152199Kakao CorpUnclassifiedIPv4 IPv61,351
AS9318SK Broadband Co LtdUnclassifiedIPv4 IPv61,287
AS4637Telstra GlobalUnclassifiedIPv4 IPv61,171
AS1299Arelion Sweden ABTransitIPv4 IPv6540
AS6939Hurricane Electric LLCTransitIPv434
AS24482SG.GSHostingIPv49

All 26 adjacent →

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.