asn.dev

Observed topology

AS132213 Cambodian Network Exchange Co., Ltd.

Unclassified APNIC

Upstreams 0 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 3
Upstream graph Who carries AS132213, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS132213 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS132213: 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 AS132213 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS24441CityLink Corporation, LTDUnclassifiedIPv610
AS7712Cambodian Network Exchange Co., Ltd.HostingIPv44
AS135375Today Communication Co.,LtdResidentialIPv44
AS45498SMART AXIATA Co., Ltd.ResidentialIPv63
AS9902NEOCOMISP LIMITED, IPTX Transit and Network Service Provider in Cambodia.UnclassifiedIPv41
AS137236TURBOTECH CO., LTD.UnclassifiedIPv41
AS137853TELNET CO.,LTDUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23764CTGNetUnclassifiedIPv4 IPv628
AS24441CityLink Corporation, LTDUnclassifiedIPv610
AS9902NEOCOMISP LIMITED, IPTX Transit and Network Service Provider in Cambodia.UnclassifiedIPv45
AS7712Cambodian Network Exchange Co., Ltd.HostingIPv44
AS135375Today Communication Co.,LtdResidentialIPv44
AS45498SMART AXIATA Co., Ltd.ResidentialIPv63
AS137236TURBOTECH CO., LTD.UnclassifiedIPv41
AS137853TELNET CO.,LTDUnclassifiedIPv41

Provenance

Where this comes from

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