Data as of Nov 20, 2026

82.195.16.0/23

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
30
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

607 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
82.195.16.0/2402
82.195.17.0/2401

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BUYPERSONALPROXY
  • BirdProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • HPROXY
  • HideProxy
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NSTPROXY_LITE
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • Q2IP
  • SOTAPROXY
  • Shifter
  • VantageProxies

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.195.0.0/198,192RU-SOVINTEL-20031021PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAOct 21, 2003abuse-b2b@beeline.ru
└ 82.195.16.0/23512FORATEC-NETForatec Communication, JSCASSIGNED PAJan 29, 2007abuse-b2b@beeline.ru
via RU-SOVINTEL-20031021

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

Who has announced 82.195.0.0/19

82.195.0.0/19

Routing history

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