asn.dev

Observed topology

AS31080 O2-AS Wirtualna Polska Media S.A.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31080: 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
AS12741Netia SAResidentialIPv462
AS6939Hurricane Electric LLCTransitIPv4 IPv630
AS1299Arelion Sweden ABTransitIPv428
AS3257GTT Communications Inc.TransitIPv4 IPv625
AS9141P4 Sp. z o.o.MobileIPv4 IPv68
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12827Wirtualna Polska Media S.A.UnclassifiedIPv41,182
AS42204Wirtualna Polska Media S.A.HostingIPv4 IPv694

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12827Wirtualna Polska Media S.A.UnclassifiedIPv41,182
AS12741Netia SAResidentialIPv4537
AS1299Arelion Sweden ABTransitIPv4390
AS6939Hurricane Electric LLCTransitIPv4 IPv6227
AS9141P4 Sp. z o.o.MobileIPv4 IPv6146
AS3257GTT Communications Inc.TransitIPv4 IPv699
AS42204Wirtualna Polska Media S.A.HostingIPv4 IPv694
AS174Cogent Communications, LLCTransitIPv422
AS24482SG.GSHostingIPv46
AS33891Core-Backbone GmbHHostingIPv44

Provenance

Where this comes from

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