Observed topology
AS17497 LGHL-AS-AP - Liasail Global Hongkong Limited
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS17497: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 976 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 767 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 707 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 488 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 455 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 252 |
| AS135067 | LOGICOM TECHNOLOGY CO.,LIMITED | Unclassified | IPv4 | 170 |
| AS63969 | Race Online Limited | Residential | IPv4 IPv6 | 65 |
| AS135338 | STARCLOUD INFORMATION LIMITED | Unclassified | IPv4 | 59 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 56 |
Transit
Downstream networks
Networks for which AS17497 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17561 | LARUS Limited | Unclassified | IPv4 | 266,698 |
| AS63099 | MADEALA TELECOM TECHNOLOGY INC | Unclassified | IPv4 | 6,038 |
| AS214432 | Zhilian Technology CO., LTD. | Unclassified | IPv4 | 2,990 |
| AS401783 | TOKALA COMMUNICATIONS INC. | Unclassified | IPv4 | 2,242 |
| AS32043 | NeoFiber Communications inc. | Unclassified | IPv4 | 1,576 |
| AS153671 | Liasail Global Hongkong Limited | Unclassified | IPv4 | 983 |
| AS13700 | NexusWave | Unclassified | IPv4 | 701 |
| AS148996 | GLOBAL COMMUNICATION NETWORK LIMITED | Unclassified | IPv4 | 468 |
| AS207550 | OCLAYER LIMITED | Unclassified | IPv4 | 464 |
| AS219410 | Kingstar(HK)Technology Limited | Unclassified | IPv4 | 360 |
Adjacency
Adjacent networks
Every AS seen directly next to AS17497 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17561 | LARUS Limited | Unclassified | IPv4 | 266,698 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 230,494 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 42,622 |
| AS63099 | MADEALA TELECOM TECHNOLOGY INC | Unclassified | IPv4 | 6,038 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 4,923 |
| AS214432 | Zhilian Technology CO., LTD. | Unclassified | IPv4 | 4,878 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 3,387 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 2,723 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,309 |
| AS401783 | TOKALA COMMUNICATIONS INC. | Unclassified | IPv4 | 2,242 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.