asn.dev

Observed topology

AS17841 NCIA-AS-KR NATIONAL INFORMATION RESOURCES SERVICE

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17841: 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 TelecomMobileIPv419,660
AS9318SK Broadband Co LtdUnclassifiedIPv45,241
AS3786LG DACOM CorporationUnclassifiedIPv43,351
AS14841AIRWAVE BROADBAND WIRELESS. INC.UnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45400Korea TelecomUnclassifiedIPv46,588
AS9950DACOM-PUBNETPLUSUnclassifiedIPv41,518
AS23575SK Broadband Co LtdUnclassifiedIPv4934

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4766Korea TelecomMobileIPv426,281
AS45400Korea TelecomUnclassifiedIPv47,254
AS9318SK Broadband Co LtdUnclassifiedIPv46,791
AS3786LG DACOM CorporationUnclassifiedIPv45,902
AS9950DACOM-PUBNETPLUSUnclassifiedIPv41,895
AS23575SK Broadband Co LtdUnclassifiedIPv41,571
AS14841AIRWAVE BROADBAND WIRELESS. INC.UnclassifiedIPv44

Provenance

Where this comes from

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