asn.dev

Observed topology

AS17579 KREONET2-AS-KR KISTI

Education RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS17579: 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
AS24482SG.GSHostingIPv4 IPv6980
AS174Cogent Communications, LLCTransitIPv4374
AS1237KISTIUnclassifiedIPv4307
AS24490Trans-Eurasia Information Network (TEIN2) - SGUnclassifiedIPv428
AS293ESnetUnclassifiedIPv427
AS2153CENICUnclassifiedIPv427
AS11537Internet2UnclassifiedIPv427
AS7660Asia Pacific Advanced Network - JapanUnclassifiedIPv426
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv424
AS6939Hurricane Electric LLCTransitIPv415

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS1237KISTIUnclassifiedIPv4 IPv610,615

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1237KISTIUnclassifiedIPv4 IPv623,177
AS24482SG.GSHostingIPv4 IPv616,271
AS174Cogent Communications, LLCTransitIPv4 IPv64,626
AS24490Trans-Eurasia Information Network (TEIN2) - SGUnclassifiedIPv4662
AS11537Internet2UnclassifiedIPv4605
AS2153CENICUnclassifiedIPv4580
AS293ESnetUnclassifiedIPv4573
AS7660Asia Pacific Advanced Network - JapanUnclassifiedIPv4 IPv6542
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4295
AS1103SURF B.V.UnclassifiedIPv4 IPv6212

All 12 adjacent →

Provenance

Where this comes from

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