Data as of Nov 15, 2026

81.9.102.0/24

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

Announcement

this exact prefix

No RPKI

Announced by

AS3216

Type

Business

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

0.39% of its addresses · 30 days

Always-on exits

100% of its exits

Providers

selling exits here

Oct 16, 2026 – Nov 14, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

2Captcha
Ake.net
BirdProxies
BottingTools
ByteProxies
Byteful
FlashProxy
GonzoProxy
Infatica
LightningProxies
NodeMaven
Proxiware
Proxy-Seller
ProxyEmpire
Proxyma
Shifter
VibeProxies
VitalExclusive
VitalProxy

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
81.9.96.0/20 since May 2005	AS20597	Residential	4 1 always on	PJSC "Vimpelcom" via now PAO Vimpelcom - formely ZAO "ELTEL"
81.9.0.0/17 since Sep 2025	AS3216	Residential	4,233 162 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.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
81.9.0.0/17	32,768	RU-SOVINTEL-20020123	PJSC "Vimpelcom" (ORG-ES15-RIPE) · RU	ALLOCATED PA	Jan 23, 2002	abuse-b2b@beeline.ru
└ 81.9.96.0/20	4,096	RU-BeeLine-NET	now PAO Vimpelcom - formely ZAO "ELTEL" (ORG-EA40-RIPE) · RU	LIR-PARTITIONED PA	Jul 5, 2012	abuse-b2b@beeline.ru
└ 81.9.102.0/24	256	RU-Bee-Line-FTTB-B2B-clients-NET	111250 Russia SOVINTEL/EDN et ELTEL	ASSIGNED PA	Oct 8, 2021	abuse-b2b@beeline.ru via RU-BeeLine-NET

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

Announcement Routing history Whois & abuse

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern: Stable
First seen: May 2022
Current origin since: May 2022 · 4.5 yr
Origin networks: 1