Home ASN LookupAS8371

AS8371 Vimpelcom-NN PJSC "Vimpelcom"

🇷🇺

Org handle: ORG-ES15-RIPE

Vimpelcom, Nizhniy Novgorod branch, fixed network

RIPE NCCallocated

Announced Prefixes (BGP)

7total

7 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)49,152

Announced (BGP)51,456

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇷🇺 RU

RIR

RIPE NCC

Status

allocated

Allocated

1997-07-03

Announced Prefixes

(BGP)7

Prefix	RPKI	IRR	Last Seen
89.189.0.0/19	No ROA	RIPE	2026-10-11
92.242.64.0/19	No ROA	RIPE	2026-10-11
95.31.49.0/24	No ROA	RIPE	2026-10-11
95.31.120.0/21	No ROA	-	2026-10-11
149.62.0.0/19	No ROA	RIPE	2026-10-11
195.98.32.0/19	No ROA	RIPE	2026-10-11
212.92.128.0/18	No ROA	RIPE	2026-10-11

Allocated Prefixes

(RIR)5

Prefix	Country	RIR	Status
89.189.0.0/19	🇷🇺 RU	RIPENCC	allocated
92.242.64.0/19	🇷🇺 RU	RIPENCC	allocated
149.62.0.0/19	🇷🇺 RU	RIPENCC	allocated
195.98.32.0/19	🇷🇺 RU	RIPENCC	allocated
212.92.128.0/18	🇷🇺 RU	RIPENCC	allocated

All 7 announced prefixes of AS8371 →

BGP Neighbours

(seen in AS paths)

Upstreams (1)

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

AS3216SOVAM PJSC "Vimpelcom"7

Downstreams (1)

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

AS57193Ruweb NN RUWEB NN1

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 AS8371 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/8371

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

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