Observed topology
AS138915 KAOPU-HK - Kaopu Cloud HK Limited
Hosting Spamhaus ASN-DROP APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS138915: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 5,572 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 3,878 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,208 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,183 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 990 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 806 |
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 IPv6 | 738 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 655 |
| AS17494 | Telecom Operator & Internet Service Provider as well | Unclassified | IPv4 IPv6 | 542 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 540 |
Transit
Downstream networks
Networks for which AS138915 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS154177 | LIGHT NODE LIMITED | Unclassified | IPv4 | 19,059 |
| AS63139 | BEDGE CO LIMITED | Unclassified | IPv4 IPv6 | 17,797 |
| AS140666 | ANY DIGITAL PTE. LTD. | Unclassified | IPv4 IPv6 | 13,340 |
| AS139341 | ACE | Hosting | IPv4 IPv6 | 2,258 |
| AS49608 | CoChen Technology LTD. | Unclassified | IPv4 | 506 |
| AS401163 | ACGNODE INC | Unclassified | IPv4 | 505 |
| AS154711 | ANYLINK NET SDN. BHD. | Unclassified | IPv4 | 357 |
| AS133478 | Tencent Cloud Computing (Beijing) Co., Ltd | Hosting | IPv4 IPv6 | 325 |
| AS58854 | Kaopu Cloud | Unclassified | IPv4 IPv6 | 317 |
| AS151397 | China Telecom | Unclassified | IPv4 IPv6 | 260 |
Adjacency
Adjacent networks
Every AS seen directly next to AS138915 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS154177 | LIGHT NODE LIMITED | Unclassified | IPv4 | 19,059 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 18,148 |
| AS63139 | BEDGE CO LIMITED | Unclassified | IPv4 IPv6 | 18,007 |
| AS140666 | ANY DIGITAL PTE. LTD. | Unclassified | IPv4 IPv6 | 13,341 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 12,257 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 6,757 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,457 |
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 IPv6 | 3,507 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 3,380 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,072 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.