asn.dev

Observed topology

AS44084 MULTIWIRE-AS Multiwire S.r.l.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44084: 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
AS12779IT.Gate S.p.A.UnclassifiedIPv4 IPv6186
AS6939Hurricane Electric LLCTransitIPv4 IPv647
AS24482SG.GSHostingIPv4 IPv65
AS59919Brainbox S.r.l.ResidentialIPv43
AS8218Zayo Infrastructure France SAUnclassifiedIPv62
AS202709NetoIP.com srlResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198167Apptc.me s.r.o.HostingIPv459
AS209387NEMEXI SRLUnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12779IT.Gate S.p.A.UnclassifiedIPv4 IPv6267
AS198167Apptc.me s.r.o.HostingIPv459
AS6939Hurricane Electric LLCTransitIPv4 IPv654
AS209387NEMEXI SRLUnclassifiedIPv632
AS24482SG.GSHostingIPv4 IPv66
AS59919Brainbox S.r.l.ResidentialIPv44
AS202709NetoIP.com srlResidentialIPv43
AS8218Zayo Infrastructure France SAUnclassifiedIPv62

Provenance

Where this comes from

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