asn.dev

Observed topology

AS41652 SAS-SHPV-FRANCE

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41652: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6215
AS35625Eurofiber France SASHostingIPv4 IPv6144
AS6939Hurricane Electric LLCTransitIPv4 IPv675
AS24482SG.GSHostingIPv4 IPv69
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv69
AS204092Association GRIFONUnclassifiedIPv4 IPv69
AS12779IT.Gate S.p.A.UnclassifiedIPv47
AS9002RETN LimitedUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39506SYNTIS SARLHostingIPv4 IPv6208

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35625Eurofiber France SASHostingIPv4 IPv6278
AS3356Level 3 Parent, LLCTransitIPv4 IPv6215
AS39506SYNTIS SARLHostingIPv4 IPv6208
AS6939Hurricane Electric LLCTransitIPv4 IPv6119
AS24482SG.GSHostingIPv4 IPv616
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv616
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv616
AS204092Association GRIFONUnclassifiedIPv4 IPv616
AS12779IT.Gate S.p.A.UnclassifiedIPv47
AS9002RETN LimitedUnclassifiedIPv66

Provenance

Where this comes from

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