Observed topology
AS9957 KINX-AS KINX
Hosting ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS9957: 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 |
|---|---|---|---|---|
| AS4766 | Korea Telecom | Mobile | IPv4 | 800 |
| AS3491 | PCCW Global HK Ltd. | Transit | IPv4 | 660 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 123 |
| AS58453 | China Mobile International Limited | Unclassified | IPv4 | 79 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 64 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 57 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 15 |
| AS9286 | KINX | Hosting | IPv4 | 4 |
| AS23764 | CTGNet | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS9957 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS10036 | DLIVE | Residential | IPv4 | 15,156 |
| AS9286 | KINX | Hosting | IPv4 IPv6 | 8,392 |
| AS20940 | Akamai International B.V. | Hosting | IPv4 IPv6 | 528 |
| AS10049 | SK Co. | Unclassified | IPv4 | 396 |
| AS139341 | ACE | Hosting | IPv4 IPv6 | 239 |
| AS984 | OCTOPUS WEB SOLUTION INC | Hosting | IPv4 IPv6 | 130 |
| AS54113 | Fastly, Inc. | Hosting | IPv4 IPv6 | 70 |
| AS1248 | HERE Global BV | Unclassified | IPv4 | 61 |
| AS152291 | NHNCLOUD | Hosting | IPv4 | 56 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 46 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9957 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS10036 | DLIVE | Residential | IPv4 | 21,977 |
| AS9286 | KINX | Hosting | IPv4 IPv6 | 19,800 |
| AS4766 | Korea Telecom | Mobile | IPv4 | 14,651 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 7,981 |
| AS3491 | PCCW Global HK Ltd. | Transit | IPv4 IPv6 | 7,751 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 6,021 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 5,597 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 2,061 |
| AS4635 | Hong Kong Internet Exchange--Route Server 1 | Unclassified | IPv4 | 875 |
| AS20940 | Akamai International B.V. | Hosting | IPv4 IPv6 | 705 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 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.