Observed topology
AS30722 VODAFONE-IT-ASN
Mobile RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS30722: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 10,297 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,916 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,739 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 302 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 283 |
| AS31543 | myNet GmbH | Residential | IPv4 | 283 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 57 |
Transit
Downstream networks
Networks for which AS30722 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203469 | Puntozero S.c.a.r.l. | Unclassified | IPv4 | 354 |
| AS12551 | ENEL S.p.A | Unclassified | IPv4 | 295 |
| AS44701 | Software Design srl | Unclassified | IPv4 | 241 |
| AS29419 | Almaviva S.p.A. | Unclassified | IPv4 | 236 |
| AS211290 | Societa' Per Azioni In Breve "IPZS S.P.A" | Unclassified | IPv4 | 178 |
| AS202017 | ASM VIGEVANO E LOMELLINA SPA | Unclassified | IPv4 | 74 |
| AS44831 | Insiel- Informatica per il sistema degli enti locali S.p.A | Unclassified | IPv4 IPv6 | 66 |
| AS202514 | KME srl | Unclassified | IPv4 | 63 |
| AS44957 | Fastweb SpA | Unclassified | IPv4 | 59 |
| AS47912 | BTICINO SpA | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS30722 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1273 | IDDQD-AS | Business | IPv4 IPv6 | 11,558 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,225 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,007 |
| AS203469 | Puntozero S.c.a.r.l. | Unclassified | IPv4 | 354 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 334 |
| AS31543 | myNet GmbH | Residential | IPv4 | 313 |
| AS12779 | IT.Gate S.p.A. | Unclassified | IPv4 | 312 |
| AS12551 | ENEL S.p.A | Unclassified | IPv4 | 295 |
| AS44701 | Software Design srl | Unclassified | IPv4 | 241 |
| AS29419 | Almaviva S.p.A. | Unclassified | IPv4 | 236 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.