asn.dev

Observed topology

AS7617 CTM (HK) Limited

Residential ARIN Cable/DSL/ISP

Upstreams 0 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 14
Adjacent (IPv6) 9
Upstream graph Who carries AS7617, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS7617 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7617: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

Networks for which AS7617 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS4609Companhia de Telecomunicacoes de Macau SARLResidentialIPv4 IPv64,847
AS17554Citic Telecom International (Data) Limited.UnclassifiedIPv4 IPv6278

Adjacency

Adjacent networks

All 14

Every AS seen directly next to AS7617 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS4609Companhia de Telecomunicacoes de Macau SARLResidentialIPv4 IPv65,809
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv62,534
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv61,723
AS6939Hurricane Electric LLCTransitIPv4 IPv6824
AS2914NTT America, Inc.TransitIPv4 IPv6811
AS17554Citic Telecom International (Data) Limited.UnclassifiedIPv4 IPv6372
AS24482SG.GSHostingIPv4 IPv691
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv481
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv672
AS9293NTT Com Asia LimitedUnclassifiedIPv420

All 14 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.