asn.dev

Observed topology

AS39605 IGUANESOLUTIONS Iguane Solutions SAS

Hosting RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS39605: 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
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6350
AS6939Hurricane Electric LLCTransitIPv4 IPv693
AS33891Core-Backbone GmbHHostingIPv416
AS24482SG.GSHostingIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv610
AS200271Iguane Solutions SASHostingIPv49
AS12779IT.Gate S.p.A.UnclassifiedIPv48
AS20766Association "Gitoyen"UnclassifiedIPv48
AS34927iFog GmbHHostingIPv48

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS200356Iguane Solutions SASHostingIPv4 IPv6218
AS200271Iguane Solutions SASHostingIPv4 IPv621

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6457
AS200356Iguane Solutions SASHostingIPv4 IPv6218
AS6939Hurricane Electric LLCTransitIPv4 IPv6168
AS200271Iguane Solutions SASHostingIPv4 IPv630
AS33891Core-Backbone GmbHHostingIPv424
AS24482SG.GSHostingIPv4 IPv618
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv618
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv618
AS20766Association "Gitoyen"UnclassifiedIPv413
AS34927iFog GmbHHostingIPv413

All 16 adjacent →

Provenance

Where this comes from

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