Data as of Nov 10, 2026

95.30.102.0/24

7 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin Nov 8, 2026
its first announcement on record

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
22
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

46 observations

Proxy providers listing exits

  • BirdProxies
  • BlurPath
  • ByteProxies
  • Byteful
  • DataImpulse
  • GSocks
  • IPFly
  • IPMUSK
  • Infatica
  • KindProxy
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.30.0.0/16
since Apr 2009
AS3216Residential762
14 always on
PJSC "Vimpelcom"
95.30.0.0/15
since Dec 2010
AS8402Residential2,519
309 always on
PJSC "Vimpelcom"
95.24.0.0/13
since Oct 2008
AS8402Residential200,355
13,839 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
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

Summary

Routing history

Pattern
Stable
First seen
Nov 8, 2026
Current origin since
Nov 8, 2026 · under a month
Origin networks
1