asn.dev

Observed topology

AS52210 CANAD-111-52210

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS52210: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6232
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv6149
AS20473The Constant Company, LLCHostingIPv64
AS205794JINZE YANGUnclassifiedIPv64
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv61
AS24482SG.GSHostingIPv61
AS34927iFog GmbHHostingIPv61
AS48185team.blue NVUnclassifiedIPv61
AS48362Stadtwerke FeldkirchResidentialIPv61
AS50300CustodianDC LimitedUnclassifiedIPv61

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS401038Accuris Technologies Ltd.UnclassifiedIPv636
AS23428ServerForge LLCUnclassifiedIPv42

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6267
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv6149
AS401038Accuris Technologies Ltd.UnclassifiedIPv636
AS20473The Constant Company, LLCHostingIPv64
AS205794JINZE YANGUnclassifiedIPv64
AS23428ServerForge LLCUnclassifiedIPv42
AS32097WholeSale Internet, Inc.HostingIPv42
AS34927iFog GmbHHostingIPv62
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv61
AS24482SG.GSHostingIPv61

All 15 adjacent →

Provenance

Where this comes from

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