asn.dev

Observed topology

AS50169 INVENTOS-AS

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS50169: 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
AS12389PJSC RostelecomResidentialIPv4 IPv6100
AS3216PJSC "Vimpelcom"MobileIPv4 IPv636
AS8359MTS PJSCMobileIPv47
AS50384iHome LLCUnclassifiedIPv47
AS50673Serverius Holding B.V.UnclassifiedIPv42
AS8218Zayo Infrastructure France SAUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS31133PJSC MegaFonMobileIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS49673Truenetwork LLCUnclassifiedIPv41

All 11 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv6100
AS3216PJSC "Vimpelcom"MobileIPv4 IPv636
AS8359MTS PJSCMobileIPv47
AS50384iHome LLCUnclassifiedIPv47
AS50673Serverius Holding B.V.UnclassifiedIPv42
AS8218Zayo Infrastructure France SAUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS31133PJSC MegaFonMobileIPv41
AS37721Virtual Technologies & SolutionsResidentialIPv41
AS49673Truenetwork LLCUnclassifiedIPv41

All 11 adjacent →

Provenance

Where this comes from

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