Data as of Nov 13, 2026

81.9.12.0/22

No anonymizer space · no proxy exits in 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.9.0.0/20
since May 2005
AS20597ResidentialPJSC "Vimpelcom"
via now PAO Vimpelcom - formely ZAO "ELTEL"
81.9.0.0/17
since Sep 2025
AS3216Residential4,254
151 always on
PJSC "Vimpelcom"

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.9.0.0/1732,768RU-SOVINTEL-20020123PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJan 23, 2002abuse-b2b@beeline.ru
└ 81.9.0.0/204,096ZAO_ELTELnow PAO Vimpelcom - formely ZAO "ELTEL" (ORG-EA40-RIPE) · RULIR-PARTITIONED PAJul 5, 2012abuse-b2b@beeline.ru
└ 81.9.12.0/221,024RU-SOVINTEL-EDN-m2m-Static-IPv4-pool-NET111250 Russia SOVINTEL/EDN et ELTELASSIGNED PAJan 15, 2016abuse-b2b@beeline.ru
via ZAO_ELTEL

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2016
Current origin since
Jan 2016 · 11 yr
Origin networks
1