asn.dev

Observed topology

AS63052 AS-CBBC

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS63052: 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
AS16866Columbia Networks Inc.ResidentialIPv4 IPv6903
AS6327Shaw CommunicationsResidentialIPv4 IPv6611
AS22652Videotron LteeResidentialIPv4 IPv653
AS9002RETN LimitedUnclassifiedIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv627
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv627
AS3130RGnet OUUnclassifiedIPv426
AS34927iFog GmbHHostingIPv426

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS16866Columbia Networks Inc.ResidentialIPv4 IPv6903
AS6327Shaw CommunicationsResidentialIPv4 IPv6611
AS22652Videotron LteeResidentialIPv4 IPv653
AS9002RETN LimitedUnclassifiedIPv4 IPv627
AS24482SG.GSHostingIPv4 IPv627
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv627
AS3130RGnet OUUnclassifiedIPv426
AS34927iFog GmbHHostingIPv426

Provenance

Where this comes from

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