asn.dev

Observed topology

AS9137 ASN-UNO Uno Communications SpA

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS9137: 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
AS6461Zayo BandwidthTransitIPv481
AS2914NTT America, Inc.TransitIPv4 IPv678
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv643
AS6939Hurricane Electric LLCTransitIPv4 IPv641
AS24482SG.GSHostingIPv4 IPv65
AS31543myNet GmbHResidentialIPv4 IPv65
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv65
AS3303Swisscom (Schweiz) AGResidentialIPv44
AS20766Association "Gitoyen"UnclassifiedIPv44
AS59919Brainbox S.r.l.ResidentialIPv44

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS9137 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 13

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv481
AS2914NTT America, Inc.TransitIPv4 IPv678
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv643
AS6939Hurricane Electric LLCTransitIPv4 IPv641
AS24482SG.GSHostingIPv4 IPv65
AS31543myNet GmbHResidentialIPv4 IPv65
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv65
AS3303Swisscom (Schweiz) AGResidentialIPv44
AS20766Association "Gitoyen"UnclassifiedIPv44
AS59919Brainbox S.r.l.ResidentialIPv44

All 13 adjacent →

Provenance

Where this comes from

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