Data as of Nov 20, 2026

195.239.208.0/23

7 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
7
1.4% of its addresses · 30 days
Always-on exits
1
14% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
47
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

3.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
195.239.209.0/2411
195.239.208.0/2406

Proxy providers listing exits

  • 2Captcha
  • 9HTTP
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
195.239.0.0/16
since May 2005
AS3216Residential657
79 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.208.0/23512RU-VIMPELCOM-SPB-Static-IP-pool-NETRussia Saint-PetersBurg VIMPELCOMASSIGNED PAMay 14, 2012abuse-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
Mar 2006
Current origin since
Mar 2006 · 21 yr
Origin networks
1