Home ASN LookupAS48541

AS48541 NVKZ-STREAM-AS MTS PJSC

🇷🇺

Org handle: ORG-ZM1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

6total

6 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)3,072

Announced (BGP)8,704

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

2008-12-09

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
94.199.76.0/22	No ROA	RIPE	-
109.95.164.0/22	No ROA	RIPE	-
178.72.104.0/21	No ROA	RIPE	-
178.72.112.0/20	No ROA	RIPE	-
178.72.115.0/24MOAS	No ROA	RIPE	-
178.72.116.0/24MOAS	No ROA	RIPE	-

Allocated Prefixes

(RIR)2

Prefix	Country	RIR	Status
94.199.76.0/22	🇷🇺 RU	RIPE	assigned
178.72.104.0/21	🇷🇺 RU	RIPE	assigned

All 6 announced prefixes of AS48541 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS8359MTS PJSC3
AS30922MTS FBN Siberia MTS PJSC3

Transfer History

Registry transfers of AS48541 between organisations.

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

Date	Resource	From	To	Type
2016-12-28	AS48541	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 AS48541 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/48541

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

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