Observed topology
AS17497 LGHL-AS-AP Liasail Global Hongkong Limited
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 | 1,324 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 707 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 690 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 220 |
| AS135067 | LOGICOM TECHNOLOGY CO.,LIMITED | Unclassified | IPv4 | 180 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 175 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 126 |
| AS135377 | UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED | Unclassified | IPv4 | 120 |
| AS133296 | Web Werks India Pvt. Ltd. | Residential | IPv4 IPv6 | 98 |
| AS135338 | STARCLOUD INFORMATION LIMITED | Unclassified | IPv4 | 61 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 59 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 30 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 24 |
| AS140570 | Hong Kong Beecloud System Technology Services Limited | Hosting | IPv4 | 23 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 17 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 17 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 | 15 |
| AS138077 | PT Abhinawa Sumberdaya Asia | Hosting | IPv4 | 4 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 2 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 | 1 |
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.
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 | 112,904 |
| AS214432 | Zhilian Technology CO., LTD. | Unclassified | IPv4 | 3,080 |
| AS63099 | MADEALA TELECOM TECHNOLOGY INC | Unclassified | IPv4 | 2,830 |
| AS401783 | TOKALA COMMUNICATIONS INC. | Unclassified | IPv4 | 1,860 |
| AS32043 | NeoFiber Communications inc. | Unclassified | IPv4 | 1,141 |
| AS153671 | Liasail Global Hongkong Limited | Unclassified | IPv4 | 1,015 |
| AS13700 | NexusWave | Unclassified | IPv4 | 359 |
| AS139057 | Edgenext Legend Dynasty Pte. Ltd. | Unclassified | IPv4 IPv6 | 273 |
| AS219410 | Kingstar(HK)Technology Limited | Unclassified | IPv4 | 183 |
| AS139734 | XINGCHEN DATA HK CO., LIMITED | Unclassified | IPv4 | 180 |
| AS213607 | WORLD FIRST COMMUNICATION LTD | Unclassified | IPv4 | 121 |
| AS402215 | Devology Tech LLC | Unclassified | IPv4 | 102 |
| AS215748 | Westeros Communications (THAILAND) CO., LTD. | Unclassified | IPv4 | 60 |
| AS214143 | SKYDIGITAL TELECOM LTD | Unclassified | IPv4 | 60 |
| AS151404 | 3GO TECHNOLOGY PTE. LTD. | Unclassified | IPv4 IPv6 | 59 |
| AS151326 | DCConnect Communication Pte. Ltd. | Residential | IPv4 | 11 |
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 | 112,904 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 88,211 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 19,693 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 13,667 |
| AS214432 | Zhilian Technology CO., LTD. | Unclassified | IPv4 | 5,180 |
| AS63099 | MADEALA TELECOM TECHNOLOGY INC | Unclassified | IPv4 | 2,830 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 | 2,494 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 IPv6 | 2,194 |
| AS401783 | TOKALA COMMUNICATIONS INC. | Unclassified | IPv4 | 1,860 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,362 |
| AS32043 | NeoFiber Communications inc. | Unclassified | IPv4 | 1,141 |
| AS153671 | Liasail Global Hongkong Limited | Unclassified | IPv4 | 1,015 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 720 |
| AS135067 | LOGICOM TECHNOLOGY CO.,LIMITED | Unclassified | IPv4 | 424 |
| AS135338 | STARCLOUD INFORMATION LIMITED | Unclassified | IPv4 | 424 |
| AS13700 | NexusWave | Unclassified | IPv4 | 359 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 318 |
| AS139057 | Edgenext Legend Dynasty Pte. Ltd. | Unclassified | IPv4 IPv6 | 277 |
| AS151404 | 3GO TECHNOLOGY PTE. LTD. | Unclassified | IPv4 IPv6 | 254 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 207 |
| AS219410 | Kingstar(HK)Technology Limited | Unclassified | IPv4 | 183 |
| AS139734 | XINGCHEN DATA HK CO., LIMITED | Unclassified | IPv4 | 180 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 164 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 163 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 | 160 |
| AS133296 | Web Werks India Pvt. Ltd. | Residential | IPv4 IPv6 | 159 |
| AS213607 | WORLD FIRST COMMUNICATION LTD | Unclassified | IPv4 | 121 |
| AS135377 | UCLOUD INFORMATION TECHNOLOGY (HK) LIMITED | Unclassified | IPv4 | 120 |
| AS402215 | Devology Tech LLC | Unclassified | IPv4 | 102 |
| AS151552 | PT Threego Technology Indonesia | Unclassified | IPv4 | 88 |
| AS214143 | SKYDIGITAL TELECOM LTD | Unclassified | IPv4 | 60 |
| AS215748 | Westeros Communications (THAILAND) CO., LTD. | Unclassified | IPv4 | 60 |
| AS140570 | Hong Kong Beecloud System Technology Services Limited | Hosting | IPv4 | 45 |
| AS151326 | DCConnect Communication Pte. Ltd. | Residential | IPv4 | 31 |
| AS138915 | Kaopu Cloud HK Limited | Hosting | IPv4 | 4 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 4 |
| AS138077 | PT Abhinawa Sumberdaya Asia | Hosting | IPv4 | 4 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 | 1 |
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.
Interconnection
Exchange presence
Internet exchanges where Packet Clearing House has a port recorded for AS17497, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 2 exchanges across 2 countries and 1 region.
| Exchange | Location | Their address | Member ports |
|---|---|---|---|
| Equinix Internet Exchange Singapore | Singapore, Singapore | 27.111.230.82 | 490 |
| Equinix Internet Exchange Hong Kong | Hong Kong, China | 2001:de8:7::1:7497:1 | 232 |
Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.
Provenance
Where this comes from
Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.
Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.
PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.