asn.dev

Observed topology

AS10352 WCTC - Solarus

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10352: 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 IPv62,993
AS174Cogent Communications, LLCTransitIPv4 IPv6576
AS24482SG.GSHostingIPv4 IPv658

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS396426-Reserved AS-UnclassifiedIPv4379
AS14334Renaissance Learning Inc.UnclassifiedIPv4251
AS17298ROEHL TRANSPORT, INC.UnclassifiedIPv462
AS21553Aspirus, Inc.UnclassifiedIPv462
AS394263Alliance Collection Agencies, INCUnclassifiedIPv457

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv63,638
AS174Cogent Communications, LLCTransitIPv4 IPv6740
AS396426-Reserved AS-UnclassifiedIPv4379
AS14334Renaissance Learning Inc.UnclassifiedIPv4251
AS24482SG.GSHostingIPv4 IPv664
AS17298ROEHL TRANSPORT, INC.UnclassifiedIPv462
AS21553Aspirus, Inc.UnclassifiedIPv462
AS394263Alliance Collection Agencies, INCUnclassifiedIPv457
AS11796Airstream Communications, LLCResidentialIPv42

Provenance

Where this comes from

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