asn.dev

Observed topology

AS200350 YANDEXCLOUD

Hosting RIPE Enterprise

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS200350: 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
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6833
AS1299Arelion Sweden ABTransitIPv4 IPv6580
AS3216PJSC "Vimpelcom"MobileIPv4525
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4425
AS6939Hurricane Electric LLCTransitIPv4 IPv6361
AS197068HLL LLCHostingIPv480
AS24482SG.GSHostingIPv4 IPv655
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv655
AS49673Truenetwork LLCUnclassifiedIPv452
AS50673Serverius Holding B.V.UnclassifiedIPv452

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215013Yandex.Cloud LLCUnclassifiedIPv4 IPv6541
AS210656Yandex.Cloud LLCUnclassifiedIPv4540

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4 IPv61,132
AS1299Arelion Sweden ABTransitIPv4 IPv6834
AS3216PJSC "Vimpelcom"MobileIPv4671
AS215013Yandex.Cloud LLCUnclassifiedIPv4 IPv6541
AS210656Yandex.Cloud LLCUnclassifiedIPv4540
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4522
AS6939Hurricane Electric LLCTransitIPv4 IPv6490
AS197068HLL LLCHostingIPv480
AS24482SG.GSHostingIPv4 IPv676
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv676

All 19 adjacent →

Provenance

Where this comes from

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