asn.dev

Observed topology

AS39479 NS3-ASN

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39479: 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
AS50877Airbeam S.r.l.HostingIPv4 IPv6224
AS50316Net Global SrlResidentialIPv4 IPv6162
AS6939Hurricane Electric LLCTransitIPv4 IPv671
AS24482SG.GSHostingIPv4 IPv69
AS3303Swisscom (Schweiz) AGResidentialIPv47
AS59919Brainbox S.r.l.ResidentialIPv47
AS8218Zayo Infrastructure France SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS35146AB NET S.R.L.UnclassifiedIPv4 IPv6154
AS206598LEVIAHUB S.P.A.UnclassifiedIPv4118
AS202523Nehos S.R.L.UnclassifiedIPv4 IPv696

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50877Airbeam S.r.l.HostingIPv4 IPv6416
AS50316Net Global SrlResidentialIPv4 IPv6284
AS35146AB NET S.R.L.UnclassifiedIPv4 IPv6154
AS206598LEVIAHUB S.P.A.UnclassifiedIPv4118
AS6939Hurricane Electric LLCTransitIPv4 IPv6111
AS202523Nehos S.R.L.UnclassifiedIPv4 IPv696
AS24482SG.GSHostingIPv4 IPv616
AS59919Brainbox S.r.l.ResidentialIPv412
AS3303Swisscom (Schweiz) AGResidentialIPv47
AS8218Zayo Infrastructure France SAUnclassifiedIPv64

Provenance

Where this comes from

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