Home ASN LookupAS209024

AS209024 MTS-CLOUD-A MTS PJSC

🇷🇺

Org handle: ORG-ZM1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

48total

46 IPv42 IPv6

IPv4 Addresses

Allocated (RIR)2,560

Announced (BGP)13,824

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)2.4×10²⁴

Prefix Limit (IPv4)

100

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

2019-04-23

Announced Prefixes

(BGP)48

Prefix	RPKI	IRR	Last Seen
62.113.64.0/24	Valid	RIPE	2026-10-11
62.113.65.0/24	No ROA	RIPE	2026-10-11
62.113.69.0/24MOAS	No ROA	RIPE	2026-10-11
77.105.181.0/24	No ROA	RIPE	2026-10-11
77.105.183.0/24	No ROA	RIPE	2026-10-11
77.105.184.0/24	No ROA	RIPE	2026-10-11
77.105.188.0/23	No ROA	RIPE	2026-10-11
80.251.156.0/24	No ROA	RIPE	2026-10-11
89.22.160.0/22	No ROA	RIPE	2026-10-11
89.22.160.0/24	No ROA	RIPE	2026-10-11

1-10 of 48

1 / 5

Allocated Prefixes

(RIR)3

Prefix	Country	RIR	Status
89.22.160.0/22	🇷🇺 RU	RIPENCC	assigned
89.22.168.0/22	🇷🇺 RU	RIPENCC	assigned
89.22.172.0/23	🇷🇺 RU	RIPENCC	assigned

All 48 announced prefixes of AS209024 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS8359MTS PJSC52

Downstreams (2)

Networks whose own prefixes AS209024 passes on: usually its customers.

AS44840KRONSHTADT JSC1
AS210443GoldApple2 RC Company1

ASPA

No ASPA

Abuse Contact

+31205354444

External Links

RIPE Whois RIPEstat

Learn more

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 AS209024 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

Open

GEThttps://api.ipctl.io/v1/asn/209024

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

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