asn.dev

Observed topology

AS23252 WTC

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23252: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,042
AS6939Hurricane Electric LLCTransitIPv4 IPv6599
AS22652Videotron LteeResidentialIPv4 IPv648
AS1403EBOXResidentialIPv4 IPv636
AS852TELUS Communications Inc.ResidentialIPv4 IPv619
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv611
AS24482SG.GSHostingIPv49
AS20473The Constant Company, LLCHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS393632The North Frontenac Telephone Corporation LimitedResidentialIPv4264
AS400363Weehooey Inc.UnclassifiedIPv4 IPv658

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,092
AS6939Hurricane Electric LLCTransitIPv4 IPv6832
AS393632The North Frontenac Telephone Corporation LimitedResidentialIPv4264
AS400363Weehooey Inc.UnclassifiedIPv4 IPv658
AS22652Videotron LteeResidentialIPv4 IPv657
AS1403EBOXResidentialIPv4 IPv652
AS852TELUS Communications Inc.ResidentialIPv4 IPv623
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv616
AS24482SG.GSHostingIPv413
AS20473The Constant Company, LLCHostingIPv63

Provenance

Where this comes from

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