asn.dev

Observed topology

AS23600 GDNSKR-KR-KR - Korea Internet Security Agency

Hosting AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23600: 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 LtdUnclassifiedIPv4 IPv6420
AS4766Korea TelecomMobileIPv4 IPv6259
AS8763DENIC eGUnclassifiedIPv4 IPv6129
AS9858Korea Internet Security AgencyHostingIPv4 IPv6119

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24151China Internet Network Infomation CenterUnclassifiedIPv4 IPv6460
AS14650Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv4 IPv6209

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9318SK Broadband Co LtdUnclassifiedIPv4 IPv6881
AS4766Korea TelecomMobileIPv4 IPv6467
AS24151China Internet Network Infomation CenterUnclassifiedIPv4 IPv6460
AS14650Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv4 IPv6209
AS8763DENIC eGUnclassifiedIPv4 IPv6129
AS9858Korea Internet Security AgencyHostingIPv4 IPv6119

Provenance

Where this comes from

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