Data as of Nov 13, 2026

195.239.26.0/24

4 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential
88% of it

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
29
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.239.0.0/16
since May 2005
AS3216Residential672
78 always on
PJSC "Vimpelcom"

Registrations in this block

The registry's network records over this block, widest first, each 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.26.0/2816kareliabcSovintelASSIGNED PAApr 4, 2006abuse-b2b@beeline.ru
via RU-SOVINTEL-971210
└ 195.239.26.16/2816SOVINTEL-N-W-NKTRIOunknownASSIGNED PAApr 19, 2006abuse-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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential22488%1
Business3213%2

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

195.239.26.0/23

Routing history

Pattern
Stable
First seen
Mar 2006
Current origin since
Mar 2006 · 21 yr
Origin networks
1