Data as of Nov 18, 2026

95.30.191.0/24

4 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
30
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

605 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • EnigmaProxy
  • Evomi
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.30.0.0/16
since Apr 2009
AS3216Residential768
8 always on
PJSC "Vimpelcom"
95.30.0.0/15
since Dec 2010
AS8402Residential2,515
289 always on
PJSC "Vimpelcom"
95.24.0.0/13
since Oct 2008
AS8402Residential201,199
12,003 always on
PJSC "Vimpelcom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.24.0.0/13524,288RU-CORBINA-20081010PJSC "Vimpelcom" (ORG-CTAM1-RIPE) · RUALLOCATED PAOct 10, 2008abuse-b2b@beeline.ru
└ 95.24.0.0 - 95.30.255.255458,752BEELINE-BROADBANDDynamic IP Pool for broadband customersASSIGNED PAMay 12, 2010abuse-b2b@beeline.ru
via RU-CORBINA-20081010

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

95.30.190.0/23

Routing history

Pattern
Stable
First seen
Mar 2026
Current origin since
Mar 2026 · 8 mo
Origin networks
1