ASN LANDING PAGE

AS200350

YandexCloud Yandex.Cloud LLC

Last updated · Apr 10, 2026

Country

Total prefixes

53

IPv4 prefixes

50

IPv6 prefixes

3

ASN summary

How to read the scale of AS200350

YandexCloud Yandex.Cloud LLC currently shows 53 prefixes and 42 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.

When is an ASN page most useful?

ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.

How should you read the country, organization, and role of AS200350?

YandexCloud Yandex.Cloud LLC is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.

What should you inspect next after the AS200350 page?

This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.

Search intents this ASN page helps cover

AS200350 ASN lookupAS200350 BGPAS200350 peersAS200350 prefixesAS200350 upstreamsYandexCloud Yandex.Cloud LLC ASN

Upstreams

Detailed data for this ASN is not available right now.

Peers

Prefix inventory

PrefixNameCountry
103.76.52.0/22AS200350
111.88.144.0/20AS200350
111.88.240.0/20AS200350
130.193.32.0/19AS200350
130.193.62.0/24AS200350
158.160.0.0/16AS200350
178.154.192.0/19AS200350
178.154.224.0/19AS200350
178.154.243.0/24AS200350
178.154.244.0/24AS200350
178.154.245.0/24AS200350
185.206.164.0/22AS200350
193.32.216.0/22AS200350
193.32.216.0/24AS200350
194.247.51.0/24AS200350
213.130.80.0/21AS200350
213.165.192.0/19AS200350
213.165.196.0/22AS200350
213.165.200.0/21AS200350
217.198.168.0/21AS200350
217.28.224.0/20AS200350
2a0b:1447:20::/44AS200350
2a0d:d6c0::/32AS200350
2a0d:d6c1::/32AS200350
31.44.8.0/21AS200350
31.44.9.0/24AS200350
37.230.168.0/23AS200350
37.230.172.0/22AS200350
46.21.244.0/22AS200350
46.243.209.0/24AS200350
46.243.210.0/23AS200350
51.250.0.0/17AS200350
51.250.112.0/21AS200350
51.250.120.0/22AS200350
51.250.126.0/24AS200350
51.250.48.0/24AS200350
51.250.50.0/23AS200350
51.250.54.0/23AS200350
62.84.112.0/20AS200350
81.26.176.0/20AS200350

Related ASN pages

Related lookups and next steps

Frequently asked questions about this ASN page

What does AS200350 represent?

AS200350 is an autonomous system number used to identify an independently operated network. The current page associates it with YandexCloud Yandex.Cloud LLC in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.

What are peers, upstreams, and prefixes useful for on the AS200350 page?

They help explain the scale, interconnection depth, and route structure of AS200350. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.

What should you do after reviewing AS200350?

The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS200350, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.

Related topics