Observed topology
AS4760 HKTIMS-AP - HKT Limited
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS4760: 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 | 34,614 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,078 |
| AS4635 | Hong Kong Internet Exchange--Route Server 1 | Unclassified | IPv4 | 1,384 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 704 |
| AS9930 | TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia | Unclassified | IPv4 | 249 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 54 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 41 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 | 38 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 | 32 |
Transit
Downstream networks
Networks for which AS4760 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS38819 | HKCSL GPRS NETWORK | Residential | IPv4 IPv6 | 3,624 |
| AS20940 | Akamai International B.V. | Hosting | IPv4 IPv6 | 176 |
| AS135146 | PCCW IMS Ltd (PCCW Business Internet Access) | Unclassified | IPv4 | 114 |
| AS4515 | PCCW IMS Ltd (PCCW Business Internet Access) | Unclassified | IPv4 | 81 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 59 |
| AS137918 | CUHK Medical Centre Limited | Unclassified | IPv4 | 46 |
Adjacency
Adjacent networks
Every AS seen directly next to AS4760 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 40,030 |
| AS38819 | HKCSL GPRS NETWORK | Residential | IPv4 IPv6 | 5,046 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,078 |
| AS4635 | Hong Kong Internet Exchange--Route Server 1 | Unclassified | IPv4 IPv6 | 1,458 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 735 |
| AS9930 | TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia | Unclassified | IPv4 | 250 |
| AS20940 | Akamai International B.V. | Hosting | IPv4 IPv6 | 176 |
| AS135146 | PCCW IMS Ltd (PCCW Business Internet Access) | Unclassified | IPv4 | 114 |
| AS4515 | PCCW IMS Ltd (PCCW Business Internet Access) | Unclassified | IPv4 | 81 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 59 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.