Autonomous system
AS200350 YANDEXCLOUD
Hosting RIPE Enterprise
Summary
Yandex Cloud
cloud hosting compute
An Autonomous System associated with Yandex Cloud, the public-cloud platform of Russian technology company Yandex.
What it's used for
- Hosting cloud compute, managed databases, storage, and other services for customers on the Yandex Cloud platform.
Notable
- An IP here identifies Yandex Cloud as the host, not the operator of whatever runs on it. Yandex operates several ASNs across its search, ads, and cloud businesses.
Interesting
- Yandex Cloud is one of the leading public-cloud providers inside the Russian market.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| MSK-IX Moscow | Moscow, Russia | 195.208.208.145 |
Transit providers
16 upstream, 2 downstream and 26 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 61 prefixes · 220K addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 63 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS200350- Registry name
- YandexCloud
- Registrant
- mnt-ru-yandexcloud-1
- Abuse contact
- cloud-abuse@yandex-team.ru
- Registered
- 2018-08-02
- Last changed
- 2026-08-13
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Yandex Cloud
- Network type
- Enterprise
- Scope
- Not Disclosed
- Traffic ratio
- Mostly Outbound
- Peering policy
- Open
- IRR as-set
AS-YACLOUD- Present at
- 11 exchanges
- Facilities
- 3 facilities
- Website
- https://cloud.yandex.com/
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 56 valid, 0 with no ROA
- ROAs
- 50 authorising AS200350
- ASPA
- no ASPA record
- IRR
- 100% registered · 56 of 56 announcements
- Route objects
- 67 naming AS200350
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 431 networks and 1,775 prefixes, as published 2026-10-11. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere