asn.dev

Observed topology

AS24441 CITYLINK-AS-KH CityLink Corporation, LTD

Unclassified APNIC NSP

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

Transit

Upstream networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS3491PCCW Global (HK) Ltd.TransitIPv4933
AS58453China Mobile International LimitedUnclassifiedIPv4748
AS6939Hurricane Electric LLCTransitIPv4 IPv6364
AS38235ANGKOR DATA COMMUNICATIONResidentialIPv4336
AS132132MyRepublic Ltd.ResidentialIPv419
AS55329Telcotech Ltd.UnclassifiedIPv412
AS132213Cambodian Network Exchange Co., Ltd.UnclassifiedIPv610
AS24482SG.GSHostingIPv45
AS38001NewMedia Express Pte LtdHostingIPv45
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS154515IZOOM SOLUTIONS CO., LTDUnclassifiedIPv4302

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3491PCCW Global (HK) Ltd.TransitIPv41,091
AS58453China Mobile International LimitedUnclassifiedIPv4748
AS38235ANGKOR DATA COMMUNICATIONResidentialIPv4480
AS6939Hurricane Electric LLCTransitIPv4 IPv6364
AS154515IZOOM SOLUTIONS CO., LTDUnclassifiedIPv4302
AS132132MyRepublic Ltd.ResidentialIPv419
AS55329Telcotech Ltd.UnclassifiedIPv412
AS132213Cambodian Network Exchange Co., Ltd.UnclassifiedIPv610
AS24482SG.GSHostingIPv45
AS38001NewMedia Express Pte LtdHostingIPv45

Provenance

Where this comes from

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