asn.dev

Observed topology

AS16080 Dalenys Payplug Enterprise SAS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16080: 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
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv665
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv612
AS6939Hurricane Electric LLCTransitIPv48
AS34019Hivane AssociationUnclassifiedIPv4 IPv62
AS5405Inter.link GmbHUnclassifiedIPv41
AS6696VERIXI SAUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS33891Core-Backbone GmbHHostingIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS50628Leonix Telecom SASUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34913Payplug Enterprise SASUnclassifiedIPv4 IPv6333

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS34913Payplug Enterprise SASUnclassifiedIPv4 IPv6333
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6208
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv4 IPv6122
AS6939Hurricane Electric LLCTransitIPv450
AS33891Core-Backbone GmbHHostingIPv48
AS34019Hivane AssociationUnclassifiedIPv4 IPv68
AS5405Inter.link GmbHUnclassifiedIPv46
AS6696VERIXI SAUnclassifiedIPv46
AS24482SG.GSHostingIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46

All 11 adjacent →

Provenance

Where this comes from

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