asn.dev

Observed topology

AS3242 ASN-ITNET REEVO S.P.A.

Hosting RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3242: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv62,390
AS1267WIND TRE S.P.A.MobileIPv4871
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv6313
AS9002RETN LimitedUnclassifiedIPv4 IPv6298
AS24482SG.GSHostingIPv4 IPv653
AS3303Swisscom (Schweiz) AGResidentialIPv448
AS59919Brainbox S.r.l.ResidentialIPv447
AS8218Zayo Infrastructure France SAUnclassifiedIPv65
AS31543myNet GmbHResidentialIPv65
AS12874Fastweb SpAResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60049CPL CONCORDIA Soc. Coop.UnclassifiedIPv465
AS56559CoreTech s.r.l.UnclassifiedIPv454

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,487
AS1267WIND TRE S.P.A.MobileIPv4871
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv6326
AS9002RETN LimitedUnclassifiedIPv4 IPv6304
AS60049CPL CONCORDIA Soc. Coop.UnclassifiedIPv465
AS24482SG.GSHostingIPv4 IPv654
AS56559CoreTech s.r.l.UnclassifiedIPv454
AS3303Swisscom (Schweiz) AGResidentialIPv449
AS59919Brainbox S.r.l.ResidentialIPv448
AS8218Zayo Infrastructure France SAUnclassifiedIPv65

All 12 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 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.