asn.dev

Observed topology

AS50272 AVUR AVUR AS

Residential RIPE NSP

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

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS50272: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6217
AS6939Hurricane Electric LLCTransitIPv4 IPv6148
AS24482SG.GSHostingIPv4 IPv616
AS34927iFog GmbHHostingIPv4 IPv616
AS50304Blix Solutions ASUnclassifiedIPv4 IPv616
AS57381Daniel HusandUnclassifiedIPv4 IPv616
AS33891Core-Backbone GmbHHostingIPv415
AS34019Hivane AssociationUnclassifiedIPv4 IPv613
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS213241TECHIT.BE SRLResidentialIPv4 IPv613

All 31 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59720Bofiber ASUnclassifiedIPv480

Adjacency

Adjacent networks

All 32

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6249
AS6939Hurricane Electric LLCTransitIPv4 IPv6160
AS59720Bofiber ASUnclassifiedIPv490
AS24482SG.GSHostingIPv4 IPv623
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv620
AS34927iFog GmbHHostingIPv4 IPv618
AS50304Blix Solutions ASUnclassifiedIPv4 IPv618
AS57381Daniel HusandUnclassifiedIPv4 IPv616
AS33891Core-Backbone GmbHHostingIPv415
AS34019Hivane AssociationUnclassifiedIPv4 IPv615

All 32 adjacent →

Provenance

Where this comes from

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