asn.dev

Observed topology

AS41405 ALTINEA-AS

Hosting RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS41405: 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
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6118
AS35625Eurofiber France SASHostingIPv4 IPv650
AS6939Hurricane Electric LLCTransitIPv436
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv65
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv65
AS3216PJSC "Vimpelcom"MobileIPv44

All 21 upstreams →

Transit

Downstream networks

inferred

Networks for which AS41405 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

All 21

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

ASNetworkTypeFamiliesPaths seen
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6118
AS35625Eurofiber France SASHostingIPv4 IPv650
AS6939Hurricane Electric LLCTransitIPv436
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65
AS24482SG.GSHostingIPv4 IPv65
AS48185team.blue NVUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv65
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv65
AS3216PJSC "Vimpelcom"MobileIPv44

All 21 adjacent →

Provenance

Where this comes from

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