Observed topology
AS45400 NICNET Korea Telecom
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS45400: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17841 | NATIONAL INFORMATION RESOURCES SERVICE | Unclassified | IPv4 | 6,588 |
Transit
Downstream networks
Networks for which AS45400 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17574 | Seoul Metropolitan Government Computer Center | Unclassified | IPv4 | 204 |
| AS10165 | KOREA CUSTOMS SERVICE | Unclassified | IPv4 | 176 |
| AS23585 | Ministry of Justice | Unclassified | IPv4 | 126 |
| AS10043 | Ministry of Science and ICT | Unclassified | IPv4 | 62 |
| AS38102 | SCOURTFAMILY | Unclassified | IPv4 | 62 |
| AS10161 | QIA | Unclassified | IPv4 | 28 |
| AS23592 | Ministry of Food and Drug Safety | Unclassified | IPv4 | 6 |
| AS38682 | National Institute of Environmental Research | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS45400 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17841 | NATIONAL INFORMATION RESOURCES SERVICE | Unclassified | IPv4 | 7,253 |
| AS17574 | Seoul Metropolitan Government Computer Center | Unclassified | IPv4 | 204 |
| AS10165 | KOREA CUSTOMS SERVICE | Unclassified | IPv4 | 176 |
| AS23585 | Ministry of Justice | Unclassified | IPv4 | 126 |
| AS10043 | Ministry of Science and ICT | Unclassified | IPv4 | 62 |
| AS38102 | SCOURTFAMILY | Unclassified | IPv4 | 62 |
| AS10161 | QIA | Unclassified | IPv4 | 28 |
| AS23592 | Ministry of Food and Drug Safety | Unclassified | IPv4 | 6 |
| AS38682 | National Institute of Environmental Research | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.