Data as of Nov 12, 2026

195.239.166.0/24

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
4
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

37 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • Proxiware
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.239.0.0/16
since May 2005
AS3216Residential674
81 always on
PJSC "Vimpelcom"

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
195.239.0.0/1665,536RU-SOVINTEL-971210PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJan 9, 2002abuse-b2b@beeline.ru
└ 195.239.166.0/24256RU-SOVINTEL-EDN-B2O-B2B-clients111250 Russia SOVINTEL/EDN B2B Clients static IP poolASSIGNED PAJul 9, 2003abuse-b2b@beeline.ru
via RU-SOVINTEL-971210

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

Summary

Routing history

Pattern
Stable
First seen
Feb 2009
Current origin since
Feb 2009 · 18 yr
Origin networks
1