Observed topology
AS138415 YANCYLIMITED-AS-HK Yancy Limited
Unclassified DROP-listed space APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS138415: 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 |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 5,454 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 1,140 |
| AS53587 | AZURE TECHNOLOGY CO., LIMITED | Hosting | IPv4 | 840 |
| AS17476 | CloudRadium (HK) Limited | Residential | IPv4 IPv6 | 609 |
| AS18013 | ASLINE LIMITED | Hosting | IPv4 | 130 |
| AS138195 | MOACK.Co.LTD | Unclassified | IPv4 | 70 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 64 |
| AS23764 | CTGNet | Unclassified | IPv4 | 9 |
| AS10099 | China Unicom Global | Unclassified | IPv4 | 3 |
Transit
Downstream networks
Networks for which AS138415 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS138195 | MOACK.Co.LTD | Unclassified | IPv4 | 1,791 |
| AS216047 | INTECLOUD CDNK LTD | Unclassified | IPv4 | 944 |
| AS137933 | CyberForest LLC. | Unclassified | IPv4 | 235 |
| AS131617 | Centroid Networking Co., Ltd. desc: 7F.-3, NO.119, SEC. 2, MINSHENG E. RD., ZHONGSHAN DIST., | Unclassified | IPv4 | 118 |
| AS401739 | RedLuff, LLC | Unclassified | IPv4 | 118 |
| AS138643 | XINYUAN INTERCONNECT COMPANY LTD | Unclassified | IPv4 | 59 |
| AS138648 | ASLINE Global Exchange | Unclassified | IPv4 | 59 |
| AS64013 | Yancy Limited | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS138415 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 7,970 |
| AS138195 | MOACK.Co.LTD | Unclassified | IPv4 | 5,055 |
| AS17476 | CloudRadium (HK) Limited | Residential | IPv4 IPv6 | 3,445 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 2,303 |
| AS216047 | INTECLOUD CDNK LTD | Unclassified | IPv4 | 944 |
| AS53587 | AZURE TECHNOLOGY CO., LIMITED | Hosting | IPv4 | 840 |
| AS137933 | CyberForest LLC. | Unclassified | IPv4 | 235 |
| AS18013 | ASLINE LIMITED | Hosting | IPv4 | 130 |
| AS131617 | Centroid Networking Co., Ltd. desc: 7F.-3, NO.119, SEC. 2, MINSHENG E. RD., ZHONGSHAN DIST., | Unclassified | IPv4 | 118 |
| AS401739 | RedLuff, LLC | Unclassified | IPv4 | 118 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.