Data as of Nov 14, 2026

81.9.28.0/24

12 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
35
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

447 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • APROXY
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • GSocks
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYSALE
  • PROXYSCRAPE
  • PROXY_CC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.9.0.0/17
since Sep 2025
AS3216Residential4,239
156 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.28.0/24256RU-BEEELINE-B2O-clients-NET111250 Russia SOVINTEL/EDNASSIGNED PADec 19, 2023abuse-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