Data as of Nov 17, 2026

81.9.102.0/23

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Business

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Always-on exits
1
50% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
20
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.5K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.9.102.0/2411
81.9.103.0/2401

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.9.0.0/17
since Sep 2025
AS3216Residential4,231
168 always on
PJSC "Vimpelcom"
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
81.9.102.0/24
since May 2022
AS3216Business1
1 always on
PJSC "Vimpelcom"
via now PAO Vimpelcom - formely ZAO "ELTEL"
81.9.103.0/24
since Oct 2021
AS3216Business1PJSC "Vimpelcom"
via now PAO Vimpelcom - formely ZAO "ELTEL"

Registrations in this block

The registry's network records over this block, widest first, each 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.96.0/204,096RU-BeeLine-NETnow PAO Vimpelcom - formely ZAO "ELTEL" (ORG-EA40-RIPE) · RULIR-PARTITIONED PAJul 5, 2012abuse-b2b@beeline.ru
└ 81.9.102.0/24256RU-Bee-Line-FTTB-B2B-clients-NET111250 Russia SOVINTEL/EDN et ELTELASSIGNED PAOct 8, 2021abuse-b2b@beeline.ru
via RU-BeeLine-NET
└ 81.9.103.0/24256RU-Bee-Line-B2B-FTTB-clients-NET111250 Russia SOVINTEL/EDN et ELTELASSIGNED PAOct 8, 2021abuse-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

Routing timeline

Covering aggregate above, the prefix's own history below

81.9.96.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1