asn.dev

Observed topology

AS50473 ECO-AS Altagen JSC

Residential RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS50473: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4646
AS20764CJSC RASCOMUnclassifiedIPv4360
AS62255BiMajLink d.o.o.UnclassifiedIPv4115
AS6939Hurricane Electric LLCTransitIPv477
AS401322NetO CorpHostingIPv458
AS24482SG.GSHostingIPv421
AS49673Truenetwork LLCUnclassifiedIPv420
AS37721Virtual Technologies & SolutionsResidentialIPv419
AS34927iFog GmbHHostingIPv47
AS50629LWLcom GmbHUnclassifiedIPv42

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51596RUSTEKO Ltd.UnclassifiedIPv49

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4646
AS20764CJSC RASCOMUnclassifiedIPv4366
AS62255BiMajLink d.o.o.UnclassifiedIPv4115
AS6939Hurricane Electric LLCTransitIPv477
AS401322NetO CorpHostingIPv458
AS49673Truenetwork LLCUnclassifiedIPv423
AS24482SG.GSHostingIPv421
AS37721Virtual Technologies & SolutionsResidentialIPv419
AS51596RUSTEKO Ltd.UnclassifiedIPv49
AS34927iFog GmbHHostingIPv47

All 14 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.