Skip to main content

AS200350

YandexCloud

-----------------------------------

Registry

Authoritative registration data

AS number
200350
Name
YandexCloud
Organisation
-----------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

54

IPv6 prefixes

3

Total announced

57

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS200350
158.160.0.0/16 IPv4 /16 not checked
51.250.0.0/17 IPv4 /17 not checked
84.201.128.0/18 IPv4 /18 not checked
89.169.128.0/18 IPv4 /18 not checked
130.193.32.0/19 IPv4 /19 not checked
153.51.32.0/19 IPv4 /19 not checked
153.51.96.0/19 IPv4 /19 not checked
178.154.192.0/19 IPv4 /19 not checked
178.154.224.0/19 IPv4 /19 not checked
213.165.192.0/19 IPv4 /19 not checked
93.77.160.0/19 IPv4 /19 not checked
111.88.144.0/20 IPv4 /20 not checked
111.88.240.0/20 IPv4 /20 not checked
217.28.224.0/20 IPv4 /20 not checked
62.84.112.0/20 IPv4 /20 not checked
81.26.176.0/20 IPv4 /20 not checked
84.252.128.0/20 IPv4 /20 not checked
213.130.80.0/21 IPv4 /21 not checked
213.165.200.0/21 IPv4 /21 not checked
217.198.168.0/21 IPv4 /21 not checked
31.44.8.0/21 IPv4 /21 not checked
51.250.112.0/21 IPv4 /21 not checked
103.76.52.0/22 IPv4 /22 not checked
185.206.164.0/22 IPv4 /22 not checked
193.32.216.0/22 IPv4 /22 not checked
213.165.196.0/22 IPv4 /22 not checked
37.230.172.0/22 IPv4 /22 not checked
46.21.244.0/22 IPv4 /22 not checked
51.250.120.0/22 IPv4 /22 not checked
84.201.184.0/22 IPv4 /22 not checked
93.77.168.0/22 IPv4 /22 not checked
153.51.96.0/23 IPv4 /23 not checked
37.230.168.0/23 IPv4 /23 not checked
46.243.210.0/23 IPv4 /23 not checked
51.250.50.0/23 IPv4 /23 not checked
51.250.54.0/23 IPv4 /23 not checked
84.201.188.0/23 IPv4 /23 not checked
89.104.112.0/23 IPv4 /23 not checked
130.193.62.0/24 IPv4 /24 not checked
178.154.243.0/24 IPv4 /24 not checked
178.154.244.0/24 IPv4 /24 not checked
178.154.245.0/24 IPv4 /24 not checked
193.32.216.0/24 IPv4 /24 not checked
194.247.51.0/24 IPv4 /24 not checked
31.44.9.0/24 IPv4 /24 not checked
46.243.209.0/24 IPv4 /24 not checked
51.250.126.0/24 IPv4 /24 not checked
51.250.48.0/24 IPv4 /24 not checked
89.232.188.0/24 IPv4 /24 not checked
89.232.189.0/24 IPv4 /24 not checked
92.255.1.0/24 IPv4 /24 not checked
92.255.13.0/24 IPv4 /24 not checked
92.255.15.0/24 IPv4 /24 not checked
92.255.3.0/24 IPv4 /24 not checked
2a0d:d6c0::/32 IPv6 /32 RPKI valid
2a0d:d6c1::/32 IPv6 /32 RPKI valid
2a0b:1447:20::/44 IPv6 /44 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS200350
Address families
CLOUD-IX MSK 100,000 Mbps IPv4 · IPv6
Eurasia Peering IX: Peering LAN 100,000 Mbps IPv4 · IPv6
GNM-IX 400,000 Mbps IPv4 · IPv6
Global-IX 400,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 400,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 200,000 Mbps IPv4
PITER-IX Helsinki 200,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 200,000 Mbps IPv4 · IPv6
PITER-IX Riga: RIX_PEERING_VLAN 200,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 200,000 Mbps IPv4 · IPv6
PITER-IX Tallinn: TLL_PEERING VLAN 200,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS200350 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

27 networks seen before AS200350 in AS paths

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS200350 in AS paths

Observed downstreams
Families
AS215013 YCCDN 472 3,565
v4 v6
AS210656 YACLOUDBMS 292 3,096
v4

No rows match “”.

Showing – of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.