Autonomous system
AS210656 YACLOUDBMS
Unclassified RIPE
Summary
Yandex Cloud
cloud hosting business
The AS handle YACLOUDBMS is operated by Yandex.Cloud LLC.
What it's used for
- The address space carries cloud infrastructure, evidenced by netnames such as
RU-YANDEXCLOUD-20081001andRU-YANDEXCLOUD-20170104registered to Yandex.Cloud LLC. - The AS announces 5376 IPv4 addresses across 9 prefixes with only 1 observed neighbour, indicating a dedicated infrastructure network rather than a transit or access provider.
- Traffic from this AS consists of cloud computing endpoints, virtual machines, and API services hosted on Yandex Cloud's infrastructure.
Notable
- Registrants for eight of the nine prefixes are Yandex.Cloud LLC, matching the AS holder; the exception is
201.50.118.0/24, registered to MT FINANCE LLC under the netnameYDX-MSK-RU-RUVDS. - The address inventory is composed of multiple /22, /23, and /24 blocks, reflecting a segmented corporate estate for cloud service delivery.
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
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS200350 | Yandex.Cloud LLC | 549 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-30, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 9 prefixes · 5.38K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 9 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS210656- Registry name
- YACLOUDBMS
- Registrant
- mnt-ru-yandexcloud-1
- Abuse contact
- cloud-abuse@yandex-team.ru
- Registered
- 2021-10-11
- Last changed
- 2024-08-07
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 100% valid · 9 valid, 0 with no ROA
- ROAs
- 13 authorising AS210656
- ASPA
- no ASPA record
- IRR
- 100% registered · 9 of 9 announcements
- Route objects
- 13 naming AS210656
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
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: 448 networks and 1,849 prefixes, as published 2026-10-30. 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