Data as of Nov 11, 2026

195.239.231.48/28

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
1
6.3% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
33
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

26 observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VitalExclusive
  • VitalProxy

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 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.231.48/2816RU-SPB-SOVINTEL-Danskebank-NETDanskebank Russia Saint Petersburg,Marata st.69-71AASSIGNED PADec 2, 2014abuse-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

195.239.230.0/23

Routing history

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