Home ASN LookupAS49154

AS49154 MTS-DOM-AS MTS PJSC

🇷🇺

Org handle: ORG-ZM1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

9total

9 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)3,072

Announced (BGP)5,888

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

2009-04-21

Announced Prefixes

(BGP)9

Prefix	RPKI	IRR	Last Seen
5.227.172.0/22	No ROA	RIPE	2026-10-10
46.148.254.0/24MOAS	No ROA	-	2026-10-10
46.148.255.0/24MOAS	No ROA	-	2026-10-10
94.229.228.0/22	No ROA	RIPE	2026-10-10
185.212.0.0/22	No ROA	RIPE	2026-10-10
188.75.231.0/24	No ROA	RIPE	2026-10-10
212.188.64.0/22	Valid	RIPE	2026-10-10
212.188.64.0/23	Valid	-	2026-10-10
212.188.66.0/23	Valid	-	2026-10-10

Allocated Prefixes

(RIR)3

Prefix	Country	RIR	Status
94.229.228.0/22	🇷🇺 RU	RIPE	assigned
185.212.0.0/22	🇷🇺 RU	RIPENCC	allocated
212.188.64.0/22	🇷🇺 RU	RIPE	assigned

All 9 announced prefixes of AS49154 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS30922MTS FBN Siberia MTS PJSC5
AS8359MTS PJSC4

Transfer History

Registry transfers of AS49154 between organisations.

AS49154Transfer · 2016-12-28
MTS PJSC
RIPE NCC
→
MTS PJSC
RIPE NCC

Date	Resource	From	To	Type
2016-12-28	AS49154	MTS PJSC RIPE NCC	MTS PJSC RIPE NCC	Transfer

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 AS49154 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/49154

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

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