asn.dev

Observed topology

AS15691 LEONET-AS-IT UAN COMPANY S.R.L.

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15691: 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
AS1267WIND TRE S.P.A.MobileIPv4493
AS174Cogent Communications, LLCTransitIPv4492
AS6939Hurricane Electric LLCTransitIPv4 IPv6236
AS3269Telecom Italia S.p.A.ResidentialIPv456
AS24482SG.GSHostingIPv4 IPv623
AS59919Brainbox S.r.l.ResidentialIPv422
AS31543myNet GmbHResidentialIPv45
AS29632Netassist International EOODUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49733TEKNE S.R.L.UnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4496
AS1267WIND TRE S.P.A.MobileIPv4493
AS6939Hurricane Electric LLCTransitIPv4 IPv6236
AS3269Telecom Italia S.p.A.ResidentialIPv456
AS24482SG.GSHostingIPv4 IPv624
AS59919Brainbox S.r.l.ResidentialIPv423
AS49733TEKNE S.R.L.UnclassifiedIPv46
AS31543myNet GmbHResidentialIPv45
AS29632Netassist International EOODUnclassifiedIPv62

Provenance

Where this comes from

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