Home ASN LookupAS41388

AS41388 ORIGINAL-AS JSC Original

🇷🇺

Org handle: ORG-ORIG1-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

3total

3 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)512

Announced (BGP)1,024

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

2021-03-06

Announced Prefixes

(BGP)3

Prefix	RPKI	IRR	Last Seen
91.232.172.0/23	No ROA	RIPE	2026-10-11
91.232.172.0/24	No ROA	RIPE	2026-10-11
91.232.173.0/24	No ROA	RIPE	2026-10-11

Allocated Prefixes

(RIR)1

Prefix	Country	RIR	Status
91.232.172.0/23	🇷🇺 RU	RIPENCC	assigned

All 3 announced prefixes of AS41388 →

BGP Neighbours

(seen in AS paths)

Upstreams (3)

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

AS3216SOVAM PJSC "Vimpelcom"1
AS8359MTS PJSC1
AS48219ThreeData 3DATA1

Transfer History

Registry transfers of AS41388 between organisations.

AS41388M&A · 2018-05-18
Mayak Communications
RIPE NCC
→
Mayak smart services Ltd.
RIPE NCC

Date	Resource	From	To	Type
2018-05-18	AS41388	Mayak Communications RIPE NCC	Mayak smart services Ltd. RIPE NCC	M&A

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 AS41388 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/41388

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

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