Data as of Nov 18, 2026

81.9.17.0/24

6 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
3
50% of its exits
Providers
43
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

4.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.9.0.0/17
since Sep 2025
AS3216Residential4,194
172 always on
PJSC "Vimpelcom"

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.17.0/24256RU-BeeLine-ChT-MyG-SeRViS-NET627000 Russia Chita, ZC-21666923ASSIGNED PAMay 16, 2022abuse-b2b@beeline.ru
via RU-SOVINTEL-20020123

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.16.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jul 2020 · 6.3 yr
Origin networks
3
Last change of origin
Jul 2020
Recorded history

History

Handoffs
2