AS215013 YCCDN Yandex.Cloud LLC

🇷🇺

Org handle: ORG-YL62-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

14total

10 IPv44 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)2,560

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)4.8×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2024-04-29

Announced Prefixes

(BGP)14

Prefix	RPKI	IRR	Last Seen
89.223.9.0/24	Valid	RIPE	-
94.131.190.0/24MOAS	Valid	RIPE	-
94.131.191.0/24	Valid	RIPE	-
188.72.103.0/24	Valid	RIPE	-
188.72.104.0/24	Valid	RIPE	-
188.72.105.0/24	Valid	RIPE	-
188.72.110.0/24	Valid	RIPE	-
188.72.111.0/24	Valid	RIPE	-
188.72.112.0/24	Valid	RIPE	-
188.72.113.0/24	Valid	RIPE	-

1-10 of 14

1 / 2

(RIR)4

Prefix	Country	RIR	Status
89.223.9.0/24	🇷🇺 RU	RIPENCC	allocated
188.72.103.0/24	🇷🇺 RU	RIPENCC	allocated
188.72.104.0/24	🇷🇺 RU	RIPE	assigned
188.72.105.0/24	🇷🇺 RU	RIPE	assigned

(seen in AS paths)

Networks AS215013 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

Abuse Contact

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS215013 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/215013" | jq