Data as of Nov 18, 2026

81.9.121.0/24

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
27
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

97 observations

Proxy providers listing exits

  • 9HTTP
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HELODATA
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.9.0.0/17
since Sep 2025
AS3216Residential4,212
169 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.121.0/24256RU-Sovam-Tele-Port-B2B-clients-NET111250 Russia SOVINTEL/EDNASSIGNED PAJan 14, 2025abuse-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.112.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jul 2019 · 7.3 yr
Origin networks
2
Last change of origin
Jul 2019
Recorded history

History

Handoffs
1