Data as of Nov 12, 2026

95.31.192.0/23

3 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 Jun 2026
its first announcement on record

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
29
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonode
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.30.0.0/15
since Dec 2010
AS8402Residential2,511
279 always on
PJSC "Vimpelcom"
95.24.0.0/13
since Oct 2008
AS8402Residential200,239
11,259 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.31.152.0 - 95.31.255.25526,624BEELINE-BROADBANDDynamic IP Pool for Broadband CustomersASSIGNED PAAug 31, 2011abuse-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
Jun 2026
Current origin since
Jun 2026 · 5 mo
Origin networks
1